| commit | a8ccc204c5daf4dae4071907499055d2dc9995db | |
| author | Johannes Sixt <johannes.sixt@telecom.at> | |
| Wed, 23 Jul 2008 07:46:35 +0000 (23 09:46 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 23 Jul 2008 19:02:57 +0000 (23 12:02 -0700) | ||
| tree | 4c18ae496933021b41783f0830dcc506ced1a1f2 | treesnapshot (tar.gz zip) |
| parent | e358f3c31e1ae9f653e9b2a6be69f5df53b4ba7e | commitdiff |
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>
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>
| git-rebase--interactive.sh | diffblobblamehistory |