diff options
author | Junio C Hamano <gitster@pobox.com> | 2014-01-15 12:26:13 -0800 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2014-01-15 15:53:51 -0800 |
commit | a74352867e689d50ee9c368f24d4a64392e27a35 (patch) | |
tree | 1569e2356883fa1bdabf282a82addc035190298a /gettext.h | |
parent | 2ac5e4470b7a17303b10ba539d8aa84e870bade9 (diff) | |
download | git-a74352867e689d50ee9c368f24d4a64392e27a35.tar.gz |
revision: propagate flag bits from tags to pointeesjc/revision-range-unpeel
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 'gettext.h')
0 files changed, 0 insertions, 0 deletions