Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: jyotish kumar <jyotishkumar725015@gmail.com>,  git@vger.kernel.org
Subject: Re: [PATCH] name-rev: update hash descriptions
Date: Sun, 27 Sep 2026 15:58:40 -0700	[thread overview]
Message-ID: <xmqqbj9iqp27.fsf@gitster.g> (raw)
In-Reply-To: <armZ28MWl9dTHDz6@fruit.crustytoothpaste.net> (brian m. carlson's message of "Sun, 27 Sep 2026 22:34:03 +0000")

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

>>  --name-only::
>> -	Instead of printing both the SHA-1 and the name, print only
>> +	Instead of printing both the object ID and the name, print only
>>  	the name.  If given with --tags the usual tag prefix of
>>  	"tags/" is also omitted from the name, matching the output
>>  	of `git-describe` more closely.
>
> This looks much better.  I didn't see any other instances of "SHA-1" in
> the documentation or "40", so this looks complete.

Great to know that somebody already did the grep for us so I do not
have to ;-)

"object ID" is the best one among a few synonyms to be used in the
description of "--name-only", as the "name" is about the textual
"name" name-rev mapped, and not about the "object identifier" that
was used as the input to the program.

      reply	other threads:[~2026-09-27 22:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27  9:54 [DOC] name-rev: --annotate-stdin docs still describe SHA-1 jyotish kumar
2026-09-27 13:50 ` brian m. carlson
2026-09-27 19:46   ` [PATCH] name-rev: update hash descriptions jyotish kumar
2026-09-27 22:34     ` brian m. carlson
2026-09-27 22:58       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqbj9iqp27.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jyotishkumar725015@gmail.com \
    --cc=sandals@crustytoothpaste.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox