summaryrefslogtreecommitdiff
path: root/remote.c
diff options
context:
space:
mode:
authorLibravatar SZEDER Gábor <szeder@ira.uka.de>2016-06-03 22:42:35 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-06-06 15:06:44 -0700
commit71abeb753fa835642acb952316266dde21d7cec6 (patch)
tree1600ef9f3f1fe231412a3a8d05759f6e803cabff /remote.c
parentGit 2.9-rc2 (diff)
downloadtgif-71abeb753fa835642acb952316266dde21d7cec6.tar.xz
reflog: continue walking the reflog past root commits
If a repository contains more than one root commit, then its HEAD reflog may contain multiple "creation events", i.e. entries whose "from" value is the null sha1. Listing such a reflog currently stops prematurely at the first such entry, even when the reflog still contains older entries. This can scare users into thinking that their reflog got truncated after 'git checkout --orphan'. Continue walking the reflog past such creation events based on the preceeding reflog entry's "new" value. The test 'symbolic-ref writes reflog entry' in t1401-symbolic-ref implicitly relies on the current behavior of the reflog walker to stop at a root commit and thus to list only the reflog entries that are relevant for that test. Adjust the test to explicitly specify the number of relevant reflog entries to be listed. Reported-by: Patrik Gustafsson <pvn@textalk.se> Signed-off-by: SZEDER Gábor <szeder@ira.uka.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'remote.c')
0 files changed, 0 insertions, 0 deletions