From: Tim Waugh <twaugh@redhat.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: patchutils-list@sourceware.org
Subject: Re: How to resolve hiccups by patch program?
Date: Fri, 05 Jan 2007 11:21:00 -0000 [thread overview]
Message-ID: <1167996075.8061.3.camel@cyberelk.elk> (raw)
In-Reply-To: <1387612361@web.de>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
I'm not entirely sure why you're asking me -- you know that patchutils
is altogether separate from diffutils (which provides diff) and from
patch, don't you? It seems to me that there is either a problem with
patch (unlikely in my opinion), or with the diff generation tool you are
using, or with the way you are using it.
In any case, patchutils is not involved.
Tim.
*/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-05 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 10:26 SF Markus Elfring
2007-01-05 11:21 ` Tim Waugh [this message]
2007-01-05 21:51 ` SF Markus Elfring
2007-01-06 15:03 ` SF Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2007-01-05 12:08 SF Markus Elfring
2007-01-04 8:04 SF Markus Elfring
2007-01-04 14:04 ` Tim Waugh
2007-01-04 22:04 ` SF Markus Elfring
2007-01-03 10:47 SF Markus Elfring
2007-01-03 12:43 ` Tim Waugh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1167996075.8061.3.camel@cyberelk.elk \
--to=twaugh@redhat.com \
--cc=elfring@users.sourceforge.net \
--cc=patchutils-list@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).