tree d88e5bf8408104d8ed270e64459e9367f8fcfa39
parent e1cfff676549cdcd702cbac105468723ef2722f4
author Junio C Hamano <gitster@pobox.com> 1600998286 -0700
committer Junio C Hamano <gitster@pobox.com> 1601068157 -0700

t1506: rev-parse A..B and A...B

Because these constructs can be used to parse user input to be
passed to rev-list --objects, e.g.

	range=$(git rev-parse v1.0..v2.0) &&
	git rev-list --objects $range | git pack-objects --stdin

the endpoints (v1.0 and v2.0 in the example) are shown without
peeling them to underlying commits, even when they are annotated
tags.  Make sure it stays that way.

While at it, ensure "rev-parse A...B" also keeps the endpoints A and
B unpeeled, even though the negative side (i.e. the merge-base
between A and B) has to become a commit.

Signed-off-by: Junio C Hamano <gitster@pobox.com>