Git development
 help / color / mirror / Atom feed
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 09:32:11 -0400	[thread overview]
Message-ID: <954865cf-5984-4e0d-9e8c-7c874896a1f2@app.fastmail.com> (raw)
In-Reply-To: <V2_datam_to_glossary.c24@msgid.xyz>



On Sun, Aug 23, 2026, at 7:32 AM, kristofferhaugsbakk@fastmail.com wrote:
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> We linked from the glossary to the data model page in the last commit.
> It can also be useful to link the other way for readers who might want
> to reference more terminology.
>
> Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
> ---
>
> Notes (series):
>     v1:
>     But: maybe the See Also link is enough here?
>    
>     > a comprehensive terminology reference
>    
>     This is descriptive or aspirational. Either works.
>
>  Documentation/gitdatamodel.adoc | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> 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. 
Also "comprehensive terminology reference" might be a bit aspirational
like you say. Maybe just "terminology reference"?

Thanks for adding these links! 

- Julia

  reply	other threads:[~2026-09-02 13:32 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 [this message]
2026-09-02 17:04       ` Kristoffer Haugsbakk
2026-09-02 17:08         ` Julia Evans
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=954865cf-5984-4e0d-9e8c-7c874896a1f2@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