From: "Julia Evans" <julia@jvns.ca>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>,
git@vger.kernel.org
Cc: "Kristoffer Haugsbakk" <code@khaugsbakk.name>,
"Patrick Steinhardt" <ps@pks.im>
Subject: Re: [PATCH v2 4/4] doc: datamodel: link to the glossary
Date: Wed, 02 Sep 2026 13:08:01 -0400 [thread overview]
Message-ID: <5e12e3ad-a80c-4c7b-81f7-e028e461fdd1@app.fastmail.com> (raw)
In-Reply-To: <d0430082-3f19-4724-ac95-1efc1f9143e1@app.fastmail.com>
On Wed, Sep 2, 2026, at 1:04 PM, Kristoffer Haugsbakk wrote:
> 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.
>> 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. :·)
next prev parent reply other threads:[~2026-09-02 17:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 18:55 [PATCH 0/4] doc: advertize gitdatamodel(1) kristofferhaugsbakk
2026-08-20 18:55 ` [PATCH 1/4] doc: git: list gitdatamodel(7) as a concept guide kristofferhaugsbakk
2026-08-21 12:22 ` Patrick Steinhardt
2026-08-20 18:55 ` [PATCH 2/4] doc: git: link to the gitdatamodel(7) tutorial kristofferhaugsbakk
2026-08-21 12:22 ` Patrick Steinhardt
2026-08-21 13:16 ` Kristoffer Haugsbakk
2026-08-20 18:55 ` [PATCH 3/4] doc: glossary: link four of the terms to gitdatamodel(7) kristofferhaugsbakk
2026-08-20 18:55 ` [PATCH 4/4] doc: datamodel: link to the glossary kristofferhaugsbakk
2026-08-23 11:32 ` [PATCH v2 0/4] doc: advertize gitdatamodel(1) kristofferhaugsbakk
2026-08-23 11:32 ` [PATCH v2 1/4] doc: git: list gitdatamodel(7) as a concept guide kristofferhaugsbakk
2026-08-23 11:32 ` [PATCH v2 2/4] doc: git: link to the gitdatamodel(7) tutorial kristofferhaugsbakk
2026-08-23 11:32 ` [PATCH v2 3/4] doc: glossary: link four of the terms to gitdatamodel(7) kristofferhaugsbakk
2026-08-23 11:32 ` [PATCH v2 4/4] doc: datamodel: link to the glossary kristofferhaugsbakk
2026-09-02 13:32 ` Julia Evans
2026-09-02 17:04 ` Kristoffer Haugsbakk
2026-09-02 17:08 ` Julia Evans [this message]
2026-08-31 7:19 ` [PATCH v2 0/4] doc: advertize gitdatamodel(1) Patrick Steinhardt
2026-09-02 13:20 ` Kristoffer Haugsbakk
2026-09-05 17:28 ` [PATCH v3 " kristofferhaugsbakk
2026-09-05 17:28 ` [PATCH v3 1/4] doc: git: list gitdatamodel(7) as a concept guide kristofferhaugsbakk
2026-09-05 17:28 ` [PATCH v3 2/4] doc: git: link to the gitdatamodel(7) tutorial kristofferhaugsbakk
2026-09-05 17:28 ` [PATCH v3 3/4] doc: glossary: link four of the terms to gitdatamodel(7) kristofferhaugsbakk
2026-09-05 17:28 ` [PATCH v3 4/4] doc: datamodel: link to the glossary kristofferhaugsbakk
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=5e12e3ad-a80c-4c7b-81f7-e028e461fdd1@app.fastmail.com \
--to=julia@jvns.ca \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=ps@pks.im \
/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