git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] glossary: use "object ID" as the canonical term

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 26, 2026, 17:08 UTC
Message-ID
<xmqqecdcs83z.fsf@gitster.g>
In-Reply-To
<pull.2282.git.1793019999896.gitgitgadget@gmail.com>
"Julia Evans via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 6 quoted lines
> 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.
Show 9 quoted lines
>
> 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.
Previous: Julia Evans via GitGitGadgetNext: Ben Knoble
Message 2 of 10 in “glossary: use "object ID" as the canonical term”
  1. glossary: use "object ID" as the canonical termJulia Evans via GitGitGadget, Oct 26, 2026
  2. Junio C HamanoOct 26, 2026
  3. Ben KnobleOct 27, 2026
  4. Junio C HamanoOct 27, 2026
  5. D. Ben KnobleOct 27, 2026
  6. D. Ben KnobleOct 27, 2026
  7. Junio C HamanoOct 27, 2026
  8. D. Ben KnobleOct 27, 2026
  9. Julia EvansOct 27, 2026
  10. Junio C HamanoOct 28, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.