summaryrefslogtreecommitdiff
path: root/git-submodule.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Sixt <johannes.sixt@telecom.at>2008-07-23 09:46:35 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2008-07-23 12:02:57 -0700
commita8ccc204c5daf4dae4071907499055d2dc9995db (patch)
tree4c18ae496933021b41783f0830dcc506ced1a1f2 /git-submodule.sh
parentsort_in_topological_order(): avoid setting a commit flag (diff)
downloadtgif-a8ccc204c5daf4dae4071907499055d2dc9995db.tar.xz
rebase -i: When an 'edit' stops, mention the commit
In a rebase session where more than one commit is to be 'edit'ed, and the user spends considerable time to 'edit' a commit, it is easy to forget what one wanted to 'edit' at the individual commits. It would be helpful to see at which commit the rebase stopped. Incidentally, if the rebase stopped due to merge conflicts or other errors, the commit was already reported ("Could not apply $sha1..."), but when rebase stopped after successfully applying an "edit" commit, it would not mention it. With this change the commit is reported. Signed-off-by: Johannes Sixt <johannes.sixt@telecom.at> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-submodule.sh')
0 files changed, 0 insertions, 0 deletions