| commit | 5d8863954f077d2c262d5cc4fc669947ff23d6d5 | |
| author | Johannes Sixt <j6t@kdbg.org> | |
| Fri, 4 May 2012 18:14:48 +0000 (4 20:14 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 4 May 2012 19:42:27 +0000 (4 12:42 -0700) | ||
| tree | 56aaf37abe80507c48f69e60fac116d46355b05a | treesnapshot (tar.gz zip) |
| parent | f94920993a0a1ba7916618e2ab458d5d4fb21e94 | commitdiff |
checkout (detached): truncate list of orphaned commits at the new HEAD
When git checkout switches from a detached HEAD to any other commit, then
all orphaned commits were listed in a warning:
Warning: you are leaving 2 commits behind...:
a5e5396 another fixup
6aa1af6 fixup foo
But if the new commit is actually one from this list (6aa1af6 in this
example), then the list in the warning can be truncated at the new HEAD,
because history beginning at HEAD is not "left behind". This makes it so.
Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When git checkout switches from a detached HEAD to any other commit, then
all orphaned commits were listed in a warning:
Warning: you are leaving 2 commits behind...:
a5e5396 another fixup
6aa1af6 fixup foo
But if the new commit is actually one from this list (6aa1af6 in this
example), then the list in the warning can be truncated at the new HEAD,
because history beginning at HEAD is not "left behind". This makes it so.
Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin/checkout.c | diffblobblamehistory | |
| t/t2020-checkout-detach.sh | diffblobblamehistory |