Michael Haggerty writes:
> On 04/02/2013 05:45 PM, Junio C Hamano wrote:
>
>> 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 i
On 04/02/2013 05:45 PM, Junio C Hamano wrote:
> Michael Haggerty 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 th
Michael Haggerty 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 c
While I was in the middle of suggesting documentation for this new
syntax, I discovered that you already added documentation to your repo
but didn't mention the new version on the mailing list (or maybe I
overlooked it). It would be helpful if you would submit your own
changes to the mailing list
A string that names an object can be suffixed with ^{type} peeler to
say "I have this object name; peel it until you get this type. If
you cannot do so, it is an error". v1.8.2^{commit} asks for a commit
that is pointed at an annotated tag v1.8.2; v1.8.2^{tree} unwraps it
further to the top-level
5 matches
Mail list logo
