From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Tim Waugh <twaugh@redhat.com>
Cc: patchutils-list@sourceware.org
Subject: Re: How to resolve hiccups by patch program?
Date: Sat, 06 Jan 2007 15:03:00 -0000 [thread overview]
Message-ID: <459FBA13.1020603@users.sourceforge.net> (raw)
In-Reply-To: <1167996075.8061.3.camel@cyberelk.elk>
> In any case, patchutils is not involved.
>
But let us see how useful your software is for other usual applications.
I did not get the expected result by the filterdiff command. So I have
tried an alternative way to extract something.
$ splitdiff -a const4.patch
Files for 76 parts were successfully created. I've looked at the first
one. "const4.patch.part001" contains two lines at the end that should
belong to the next file, shouldn't they?
It seems that the text "Index: apps/app_alarmreceiver.c" and "===== ..."
belongs to a kind of extension. Would you like to support that?
http://en.wikipedia.org/wiki/Diff#Extensions
Would you like to add a command option that the part number will not be
written as a suffix of the file name?
(I would prefer a name like "test.1.part.patch" to make the work with
file associations easier.)
Regards,
Markus
next prev parent reply other threads:[~2007-01-06 15:03 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
2007-01-05 21:51 ` SF Markus Elfring
2007-01-06 15:03 ` SF Markus Elfring [this message]
-- 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=459FBA13.1020603@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=patchutils-list@sourceware.org \
--cc=twaugh@redhat.com \
/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).