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

Re: [PATCH v2 4/4] doc: datamodel: link to the glossary

From
Julia Evans <julia@jvns.ca>
Date
Sep 2, 2026, 17:08 UTC
Message-ID
<5e12e3ad-a80c-4c7b-81f7-e028e461fdd1@app.fastmail.com>
In-Reply-To
<d0430082-3f19-4724-ac95-1efc1f9143e1@app.fastmail.com>
On Wed, Sep 2, 2026, at 1:04 PM, Kristoffer Haugsbakk wrote:
Show 20 quoted lines
> On Wed, Sep 2, 2026, at 15:32, Julia Evans wrote:
>> On Sun, Aug 23, 2026, at 7:32 AM, kristofferhaugsbakk@fastmail.com wrote:
>>>[snip]
>>> diff --git a/Documentation/gitdatamodel.adoc b/Documentation/gitdatamodel.adoc
>>> index dcfdff0346f..d588630e633 100644
>>> --- a/Documentation/gitdatamodel.adoc
>>> +++ b/Documentation/gitdatamodel.adoc
>>> @@ -24,6 +24,8 @@ Git's core operations use 4 kinds of data:
>>>  3. <<index,The index>>, also known as the staging area
>>>  4. <<reflogs,Reflogs>>: logs of changes to references ("ref log")
>>>
>>> +See linkgit:gitglossary[7] for a comprehensive terminology reference.
>>
>> I'd prefer to put this in SEE ALSO instead.
>
> It’s also in See Also. Do you mean put the whole sentence in See Also
> instead of just this link? I have never seen See Also be used for more
> than just a comma-separated list of links.
>
> I’m also okay with just dropping it.

Ah, I didn't see it in See Also, I'm still struggling to get used to this email-based patch review workflow :)

I think just dropping it is fine.
Show 20 quoted lines
>> Also "comprehensive terminology reference" might be a bit aspirational
>> like you say. Maybe just "terminology reference"?
>
> Yeah. The idea behind having any adjective or modifier was that just
> “terminology reference” seemed to not contrast the roles of these two
> pages enough. Since they are both about terminology after all, just one
> of them drills down into the core concepts/terminology.
>
> Or it could be
>
>    ... terminology reference for all of Git.
>
> Which seems a bit much and wordy. Or maybe
>
>    ... general terminology reference.
>
>>
>> Thanks for adding these links!
>
> Thanks for reviewing. :·)
Previous: Kristoffer HaugsbakkNext: Patrick Steinhardt
Message 16 of 23 in “doc: advertize gitdatamodel(1)”
  1. 0/4 doc: advertize gitdatamodel(1)kristofferhaugsbakk@fastmail.com, Aug 20, 2026
  2. 1/4 doc: git: list gitdatamodel(7) as a concept guidekristofferhaugsbakk@fastmail.com, Aug 20, 2026
  3. Patrick SteinhardtAug 21, 2026
  4. 2/4 doc: git: link to the gitdatamodel(7) tutorialkristofferhaugsbakk@fastmail.com, Aug 20, 2026
  5. Patrick SteinhardtAug 21, 2026
  6. Kristoffer HaugsbakkAug 21, 2026
  7. 3/4 doc: glossary: link four of the terms to gitdatamodel(7)kristofferhaugsbakk@fastmail.com, Aug 20, 2026
  8. 4/4 doc: datamodel: link to the glossarykristofferhaugsbakk@fastmail.com, Aug 20, 2026
  9. 0/4 doc: advertize gitdatamodel(1)kristofferhaugsbakk@fastmail.com, Aug 23, 2026
  10. 1/4 doc: git: list gitdatamodel(7) as a concept guidekristofferhaugsbakk@fastmail.com, Aug 23, 2026
  11. 2/4 doc: git: link to the gitdatamodel(7) tutorialkristofferhaugsbakk@fastmail.com, Aug 23, 2026
  12. 3/4 doc: glossary: link four of the terms to gitdatamodel(7)kristofferhaugsbakk@fastmail.com, Aug 23, 2026
  13. 4/4 doc: datamodel: link to the glossarykristofferhaugsbakk@fastmail.com, Aug 23, 2026
  14. Julia EvansSep 2, 2026
  15. Kristoffer HaugsbakkSep 2, 2026
  16. Julia EvansSep 2, 2026
  17. Patrick SteinhardtAug 31, 2026
  18. Kristoffer HaugsbakkSep 2, 2026
  19. 0/4 doc: advertize gitdatamodel(1)kristofferhaugsbakk@fastmail.com, Sep 5, 2026
  20. 1/4 doc: git: list gitdatamodel(7) as a concept guidekristofferhaugsbakk@fastmail.com, Sep 5, 2026
  21. 2/4 doc: git: link to the gitdatamodel(7) tutorialkristofferhaugsbakk@fastmail.com, Sep 5, 2026
  22. 3/4 doc: glossary: link four of the terms to gitdatamodel(7)kristofferhaugsbakk@fastmail.com, Sep 5, 2026
  23. 4/4 doc: datamodel: link to the glossarykristofferhaugsbakk@fastmail.com, Sep 5, 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.