Thread (1 message) 1 message, 1 author, 2020-06-05

Re: name-ref on annotated-tags is null terminated, but lightweight tags arent

From: Junio C Hamano <hidden>
Date: 2020-06-05 17:59:17

Max Resnick [off-list ref] writes:
Thanks Junio for the quick response.
quoted
Presumably the long hexadecimal are supposed to be on the same line 
as the "name-rev" command itself?                                   
Yes, sorry I didn't see that the formatting was broken before I sent.
quoted
The suffix "^0" (which has nothing to do 
with null-termination) means "I do not mean the tag object itself, 
but the object that is pointed by it".                             
Ok, thanks. I need to unpack that a bit more. I tried to dig around in
the man to see if there was indication if that's what was expected but
didn't find anything at less for name-rev.
"git help revisions" has this, which may help.

       <rev>^[<n>], e.g. HEAD^, v1.5.1^0
                  A suffix ^ to a revision parameter means the first
                  parent of that commit object.  ^<n> means the
                  <n>th parent (i.e.  <rev>^ is equivalent to
                  <rev>^1).  As a special rule, <rev>^0 means the
                  commit itself and is used when <rev> is the object
                  name of a tag object that refers to a commit
                  object.

The help text in "git help name-rev" only says "names suitable for
human digestion", which may want to be clarified.

Thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help