Re: [PATCH] doc: add a explanation of Git's data model

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 7, 2025, 20:01 UTC
Message-ID: <xmqqwm56iiq1.fsf@gitster.g>
In-Reply-To: <ede082ad-5031-4b55-8576-0a6315f16b70@app.fastmail.com>

"Julia Evans" <julia@jvns.ca> writes:

> I think it's useful to refer this as an "ID", because usually we call it a
> "commit ID" or "tag ID" and not a "commit name" or "tag name"
> and it makes it more clear that "object name" and "commit ID"
> refer to the same identifier.

It is a bit funny that they do not exactly align.

    "object name" aka "object ID"
    "$type object name" aka "$type ID" for type in (commit, blob, tree, tag)

In any case, we should add "object ID" and other "$type ID" to the glossary, if you are going to use it very often. We have entries for spelled out "identifier" but I do not think "ID" is there yet.

Thanks.

$ 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.