All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eli Carter <eli.carter@inet.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [OT] patch splitting util(s)?
Date: Mon, 14 Apr 2003 17:26:57 -0500	[thread overview]
Message-ID: <3E9B35B1.1020809@inet.com> (raw)
In-Reply-To: 20030414215128.GA24096@suse.de

Dave Jones wrote:
> On Mon, Apr 14, 2003 at 04:46:32PM -0500, Eli Carter wrote:
> 
>  > I didn't have much luck with googling.  I think the words I used are too 
>  > generic.  :/
>  
> Google for diffsplit. Its part of Tim Waugh's patchutils.
> Patchutils should be part of pretty much every distro these days too.

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 could then use directories and 'mv' to sort 
out the parts.  Repetative calls to 'combinediff' would suffice for 
cleaning up the ensuing mess, I think.  Hmm...  That would get me to the 
hunk level, but not the sub-hunk, though editdiff/rediff might help there.

Thanks,

Eli
--------------------. "If it ain't broke now,
Eli Carter           \                  it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------


  reply	other threads:[~2003-04-14 22:15 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 [this message]
     [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

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=3E9B35B1.1020809@inet.com \
    --to=eli.carter@inet.com \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.