git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yann Dirson <yann.dirson@bertin.fr>
To: git@vger.kernel.org
Subject: Re: WANTED: patch splitting tool - waypoints
Date: Mon, 3 May 2010 06:43:18 +0000 (UTC)	[thread overview]
Message-ID: <loom.20100503T082814-180@post.gmane.org> (raw)
In-Reply-To: 20100502115842.GA11607@brong.net

Bron Gondwana <brong <at> brong.net> writes:
> My toolkit is missing a tool.  I've never seen it
> or anything like it, but I can describe it - and
> hopefully someone else knows if it exists.
> 
> It's basically a combination of git rebase -i and
> git add -p.  Something that allows you to split
> either a single patch or a series of patches that
> had bad "waypoints".

Right, this is a use-case I also commonly have, and nowadays I
mostly use the rebase -i approach already described, combined with
the use of git-gui for easy selection.

One additional trick I sometimes use, when I have reordered/squashed/split
a couple of commits, is things like "git checkout @{1}" to catch any missing
changes I could have lost while working.

Some time ago I was using stgit extensively, and had developped
a couple of scripts to support that workflow.  You will find them
in the contrib/ directory of the stgit repo, and in the
stgit-contrib debian package.  Note that I did not use them much
lately, and they may need some tweeking to work with recent
git/stgit.

The still-relevant scripts are:
  * stg-fold-files-from: pick specific hunks from another patch up the stack
  * stg-dispatch: dispatch specific hunks into another patch down the stack

      parent reply	other threads:[~2010-05-03  6:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-02 11:58 WANTED: patch splitting tool - waypoints Bron Gondwana
2010-05-02 15:17 ` Matthieu Moy
2010-05-02 15:20 ` Matthieu Moy
2010-05-02 23:40   ` Bron Gondwana
2010-05-03  6:31     ` Matthieu Moy
2010-05-02 21:10 ` Robin Rosenberg
2010-05-03  6:43 ` Yann Dirson [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=loom.20100503T082814-180@post.gmane.org \
    --to=yann.dirson@bertin.fr \
    --cc=git@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 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).