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

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

From
Julia Evans <julia@jvns.ca>
Date
Oct 27, 2026, 22:34 UTC
Message-ID
<fbe5442b-6f01-4a23-8282-6a940b89da43@app.fastmail.com>
In-Reply-To
<xmqqh5i7j6km.fsf@gitster.g>
On Tue, Oct 27, 2026, at 3:18 PM, Junio C Hamano wrote:
Show 12 quoted lines
> "D. Ben Knoble" <ben.knoble@gmail.com> writes:
>
>> I can't speak for Julia, but I read her attempt here to clarify things
>> in line with the ways folks usually use "ID" vs. "name." Of course we
>> don't always want to let what other people say dictate our
>> terminology, but in cases where we can make things easier for folks to
>> understand by using vocabulary in line with their expectations rather
>> than subverting it, I think that's a worthy goal.
>
> That goes both ways.  You can tell that to those who are subverting
> terminology that have clearly been documented for the past 20 years
> in our official glossary ;-).

I'll only say that I genuinely thought this might be a fairly uncontroversial change. Obviously I was wrong about that :)

I'll drop this.
- Julia
Previous: D. Ben KnobleNext: Junio C Hamano
Message 9 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.