| commit | 53f2ffa80c1c5ea5feb9fbe7432bf7106cf3047e | |
| author | Jeff King <peff@peff.net> | |
| Fri, 27 May 2011 20:16:14 +0000 (27 16:16 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 27 May 2011 22:52:03 +0000 (27 15:52 -0700) | ||
| tree | 3e5d5c5dbd67ca9d55c8da29b34438b16766f30b | treesnapshot (tar.gz zip) |
| parent | ea69619cd1081359e73e597a76fcf6444f222f2d | commitdiff |
rebase: write a reflog entry when finishing
When we finish a rebase, our detached HEAD is at the final
result. We update the original branch ref with this result,
and then point the HEAD symbolic ref at the updated branch.
We write a reflog for the branch update, but not for the
update of HEAD.
Because we're already at the final result on the detached
HEAD, moving to the branch actually doesn't change our
commit sha1 at all. So in that sense, a reflog entry would
be pointless.
However, humans do read reflogs, and an entry saying "rebase
finished: returning to refs/heads/master" can be helpful in
understanding what is going on.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When we finish a rebase, our detached HEAD is at the final
result. We update the original branch ref with this result,
and then point the HEAD symbolic ref at the updated branch.
We write a reflog for the branch update, but not for the
update of HEAD.
Because we're already at the final result on the detached
HEAD, moving to the branch actually doesn't change our
commit sha1 at all. So in that sense, a reflog entry would
be pointless.
However, humans do read reflogs, and an entry saying "rebase
finished: returning to refs/heads/master" can be helpful in
understanding what is going on.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| git-rebase--interactive.sh | diffblobblamehistory | |
| git-rebase.sh | diffblobblamehistory | |
| t/t3404-rebase-interactive.sh | diffblobblamehistory |