All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eli Carter <eli.carter@inet.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [OT] patch splitting util(s)?
Date: Mon, 14 Apr 2003 16:46:32 -0500	[thread overview]
Message-ID: <3E9B2C38.4020405@inet.com> (raw)

A bit off-topic, but something tangentally related to this list...

Is anyone aware of a utility that helps with splitting a (large) patch 
into multiple patches at a hunk (or better, a sub-hunk) level?

I'm visualizing a GUI (or similar) that lets you right-click on a hunk 
and get a list of sub-patches or the option to create a new sub-patch, 
and moves the hunk to the selected sub-patch.  (I use the term 
'sub-patch', but in theory, you could load a set of patches, then 
shuffle hunks around.)  And lets you go to the sub-patches and move 
hunks from there to another patch.

A vim or emacs script/plugin would probably make the most sense.  (I'm a 
vim user, so I'm not familiar with what emacs provides, but I didn't see 
this functionality after a very quick look.)

I didn't have much luck with googling.  I think the words I used are too 
generic.  :/

Anyone know of something like this?

TIA,

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 21:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 21:46 Eli Carter [this message]
2003-04-14 21:51 ` [OT] patch splitting util(s)? 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

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=3E9B2C38.4020405@inet.com \
    --to=eli.carter@inet.com \
    --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.