On 04/02/2013 05:45 PM, Junio C Hamano wrote:
> Michael Haggerty <[email protected]> writes:
>
>> Off topic: Your patch reminds me of something else that surprised me:
>> there is no "$userstring^{tag}". I suppose it would be a bit ambiguous,
>> given that tags can point at tags, and it would also be less useful than
>> the other suffixes. But its absence irked the completionist in me :-)
>
> Yes, unfortunately, foo^{type} means "start from foo, and until what
> you are looking at it is of type, repeatedly peel to see if you can
> get to an object of that type, or stop and report an error". If a
> tag A points at another tag B, which in turn points at an object C,
> you will never see B by applying usual peeling operator.
>
> Also, v1.8.2^{tag} would be give the tag itself, while master^{tag}
> would not report the commit "master" but would error out, which
> would be useless. You are better off doing `git cat-file -t foo`
> and seeing if it is a tag object at that point.
All correct, of course. But the user would never use "master^{tag}"
unless he wants a tag and nothing else, so erroring out would be exactly
the thing he wants in that case. This is no different than the
"^{commit}" part of "master^{tree}^{commit}", which correctly errors out
because a commit cannot be inferred from a tree.
Michael
--
Michael Haggerty
[email protected]
http://softwareswirl.blogspot.com/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
