[PATCH 0/2] rebase -i: Some nice-to-have behaviors for "reword"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]