From: Junio C Hamano <gitster@pobox.com>
To: Max Resnick <max.resnick@forgerock.com>
Cc: git@vger.kernel.org
Subject: Re: name-ref on annotated-tags is null terminated, but lightweight tags arent
Date: Fri, 05 Jun 2020 10:59:12 -0700 [thread overview]
Message-ID: <xmqq3679o0lr.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200605171607.rducvc4xretxacn5@forgemax.local> (Max Resnick's message of "Fri, 5 Jun 2020 10:16:07 -0700")
Max Resnick <max.resnick@forgerock.com> writes:
> Thanks Junio for the quick response.
>
>> 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.
>
>> 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.
prev parent reply other threads:[~2020-06-05 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 16:51 name-ref on annotated-tags is null terminated, but lightweight tags arent Max Resnick
2020-06-05 17:04 ` Junio C Hamano
2020-06-05 17:16 ` Max Resnick
2020-06-05 17:59 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq3679o0lr.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=max.resnick@forgerock.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).