From: Andrew Wong <andrew.kw.w@gmail.com>
To: git@vger.kernel.org
Cc: Andrew Wong <andrew.kw.w@gmail.com>
Subject: [PATCH 0/2] rebase -i: Some nice-to-have behaviors for "reword"
Date: Sun, 24 Jul 2011 23:38:31 -0400 [thread overview]
Message-ID: <1311565113-5022-1-git-send-email-andrew.kw.w@gmail.com> (raw)
I've been using the "reword" command fairly often, and these are two small
modifications that I've always wished I could do during a "reword". They're
more of a convenience than anything. Hopefully they're not derailing the
original intent of "reword" too much...
1/2:
Often times when I need to reword commit, it's because the commit message was
unclear. So when the "commit --amend" happens, I often found myself having to
do a "show HEAD" to inspect the diff to figure out what the commit was actually
doing. This patch saves me this extra step. Since this behavior isn't what
users might expect when they run "rebase -v", maybe I'm better off putting this
into a new flag, like "rebase --commit-verbose". Any thoughts?
2/2:
Sometimes when I'm rewording a bunch of commits, I'd realize that I actually
want to edit the commit that I'm current rewording, like a quick fix or
something. Or I might even want to abort the entire rebase operation
altogether. This patch provides a way to gracefully to abort the "reword".
Andrew Wong (2):
rebase -i: run "commit --amend" with verbose if rebase was called
with -v
rebase -i: interrupt rebase when "commit --amend" failed
git-rebase--interactive.sh | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
--
1.7.2.2
next reply other threads:[~2011-07-30 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 3:38 Andrew Wong [this message]
2011-07-25 3:38 ` [PATCH 1/2] rebase -i: run "commit --amend" with verbose if rebase was called with -v Andrew Wong
2011-07-25 3:38 ` [PATCH 2/2] rebase -i: interrupt rebase when "commit --amend" failed Andrew Wong
2011-07-30 11:52 ` Sverre Rabbelier
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=1311565113-5022-1-git-send-email-andrew.kw.w@gmail.com \
--to=andrew.kw.w@gmail.com \
--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).