From: Eli Carter <eli.carter@inet.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [OT] patch splitting util(s)?
Date: Thu, 24 Apr 2003 17:05:22 -0500 [thread overview]
Message-ID: <3EA85FA2.6060500@inet.com> (raw)
In-Reply-To: 20030424164503.A995@devserv.devel.redhat.com
Pete Zaitcev wrote:
>>Date: Tue, 15 Apr 2003 13:10:43 -0700
>>From: "Randy.Dunlap" <rddunlap@osdl.org>
>
>
>>| > I'm aware of patchutils. (Check the 0.2.22 Changelog ;) ) However,
>>| > splitdiff doesn't do what I'm after, from my initial look. Though now
>>| > that I think about it, it suggests an alternative solution. A
>>| > 'shatterdiff' that created one diff file per hunk in a patch would give
>>| > me basically what I want.
>>|
>>| I moaned at Tim until he caved in and added an '-s' option
>>| couple of weeks ago. It should be in a fresh rawhide srpm.
>>|
>>| Mind, you can do what you want even now, with -n (for line numbers)
>>| and a little bit of sh or perl, but all concievable solutions
>>| require several passes over the diff, which gets tiresome
>>| if you diff 2.4.9 (RH 7.2) and 2.4.18 (RH 8.0). The -s option
>>| does it in one pass.
>>
>>so when does this change show up at http://cyberelk.net/tim/patchutils/ ?
>
>
> Tim pointed out that the option is -a, not -s. It should be
> present in 0.2.22.
Almost. That does a per-file split, not a per-hunk split. And per-hunk
I have found makes splitting patches into their logical components
_much_ easier.
Thanks for the clarification though!
Eli
--------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------
prev parent reply other threads:[~2003-04-24 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 21:46 [OT] patch splitting util(s)? Eli Carter
2003-04-14 21:51 ` Dave Jones
2003-04-14 22:26 ` Eli Carter
[not found] ` <mailman.1050360781.7083.linux-kernel2news@redhat.com>
2003-04-15 0:47 ` Pete Zaitcev
2003-04-15 15:22 ` Eli Carter
2003-04-15 20:10 ` Randy.Dunlap
2003-04-24 20:45 ` Pete Zaitcev
2003-04-24 22:05 ` Eli Carter [this message]
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=3EA85FA2.6060500@inet.com \
--to=eli.carter@inet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=zaitcev@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 NNTP newsgroup(s).