From: Junio C Hamano <gitster@pobox.com>
To: "Julia Evans via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH] glossary: use "object ID" as the canonical term
Date: Mon, 26 Oct 2026 10:08:00 -0700 [thread overview]
Message-ID: <xmqqecdcs83z.fsf@gitster.g> (raw)
In-Reply-To: <pull.2282.git.1793019999896.gitgitgadget@gmail.com> (Julia Evans via GitGitGadget's message of "Mon, 26 Oct 2026 13:06:39 +0000")
"Julia Evans via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Julia Evans <julia@jvns.ca>
>
> Currently in the glossary "object name" is used as the canonical term to
> refer to an object's SHA-1 (or SHA-256) identifier. However, in several
> places in the documentation, "object name" is used with a different
> meaning, for example:
These other places should be fixed, IMHO, though.
>
> from git-rev-parse.adoc:
> Usually the object names are output in SHA-1 form (with possible
> ^ prefix); this option makes them output in a form as close to the
> original input as possible.
>
> from gitrevisions.adoc:
> Here are various ways to spell object names.
> (lists <refname>, HEAD, etc)
You can use <refname>, HEAD, etc., where the command takes object
names. It exactly refers to those 40 hexadecimal digits to identify
objects.
I'll reject this.
next prev parent reply other threads:[~2026-10-26 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 13:06 [PATCH] glossary: use "object ID" as the canonical term Julia Evans via GitGitGadget
2026-10-26 17:08 ` Junio C Hamano [this message]
2026-10-27 12:15 ` Ben Knoble
2026-10-27 17:47 ` Junio C Hamano
2026-10-27 18:00 ` D. Ben Knoble
2026-10-27 18:03 ` D. Ben Knoble
2026-10-27 19:18 ` Junio C Hamano
2026-10-27 19:24 ` D. Ben Knoble
2026-10-27 22:34 ` Julia Evans
2026-10-28 1:08 ` Junio C Hamano
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=xmqqecdcs83z.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=julia@jvns.ca \
--cc=peff@peff.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