From: Thomas Rast <trast@student.ethz.ch>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: <git@vger.kernel.org>
Subject: Re: [feature wishlist] add commit subcommand to git add -i
Date: Mon, 15 Aug 2011 14:54:29 +0200 [thread overview]
Message-ID: <201108151454.29912.trast@student.ethz.ch> (raw)
In-Reply-To: <CAJfuBxwW8Dyp8FTS13uPOBKZGL9JOEqaSOhGN+zBJ_8BHpJE3g@mail.gmail.com>
Jim Cromie wrote:
> [f]ragment would also be handy, which would break each chunk of a diff
> into a separate commit, with the summary line provided automatically
> <file> @@ -696,7 +692,7 @@ int foo ...
>
> This would help a bit with random cleanups, since rebase -i could then
> be used to
> reorder and recombine the fragments, and edit the commit messages afterwards.
>
> going further, if git rebase -i had ability to "back" a fixup patch
> back to where it should have been
This little script may be of interest to you:
http://article.gmane.org/gmane.comp.version-control.git/163621
--
Thomas Rast
trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2011-08-15 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 8:38 [feature wishlist] add commit subcommand to git add -i Jim Cromie
2011-08-14 8:48 ` Conrad Irwin
2011-08-15 0:43 ` Jim Cromie
2011-08-14 8:56 ` Ramkumar Ramachandra
2011-08-15 0:44 ` Jim Cromie
2011-08-15 12:54 ` Thomas Rast [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=201108151454.29912.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=jim.cromie@gmail.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).