summaryrefslogtreecommitdiff
path: root/t/t0202
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2014-01-15 12:26:13 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-01-15 15:53:51 -0800
commita74352867e689d50ee9c368f24d4a64392e27a35 (patch)
tree1569e2356883fa1bdabf282a82addc035190298a /t/t0202
parentrevision: mark contents of an uninteresting tree uninteresting (diff)
downloadtgif-a74352867e689d50ee9c368f24d4a64392e27a35.tar.xz
revision: propagate flag bits from tags to pointees
With the previous fix 895c5ba3 (revision: do not peel tags used in range notation, 2013-09-19), handle_revision_arg() that processes command line arguments for the "git log" family of commands no longer directly places the object pointed by the tag in the pending object array when it sees a tag object. We used to place pointee there after copying the flag bits like UNINTERESTING and SYMMETRIC_LEFT. This change meant that any flag that is relevant to later history traversal must now be propagated to the pointed objects (most often these are commits) while starting the traversal, which is partly done by handle_commit() that is called from prepare_revision_walk(). We did propagate UNINTERESTING, but did not do so for others, most notably SYMMETRIC_LEFT. This caused "git log --left-right v1.0..." (where "v1.0" is a tag) to start losing the "leftness" from the commit the tag points at. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t0202')
0 files changed, 0 insertions, 0 deletions