Git development
 help / color / mirror / Atom feed
From: kristofferhaugsbakk@fastmail.com
To: git@vger.kernel.org
Cc: Kristoffer Haugsbakk <code@khaugsbakk.name>,
	Patrick Steinhardt <ps@pks.im>, Julia Evans <julia@jvns.ca>
Subject: [PATCH v3 0/4] doc: advertize gitdatamodel(1)
Date: Sat,  5 Sep 2026 19:28:11 +0200	[thread overview]
Message-ID: <V3_CV_doc_datamodel_advertize.c7e@msgid.xyz> (raw)
In-Reply-To: <CV_doc_datamodel_advertize.bea@msgid.xyz>

From: Kristoffer Haugsbakk <code@khaugsbakk.name>

Topic name (applied): kh/doc-datamodel

Topic summary: gitdatamodel(7) is not linked to from anywhere. Let’s
mention it on other documentation pages and add a link to the glossary on
the data model page.

§ Testing

Testing done on v1. No tests done for v2 or v3.

§ Changes in v3

Thanks to Patrick and Julia for reviewing.

Following up on Julia’s review. See the interdiff/range diff and
patch notes. The patch notes also documents the changes from the
previous rounds by the way.

§ Link to v2

https://lore.kernel.org/git/V2_CV_doc_datamodel_advertize.c20@msgid.xyz/#t

§ Aside about context lines in gitlossary(7)

(see v1 & v2; no one commented on this)

[1/4] doc: git: list gitdatamodel(7) as a concept guide
[2/4] doc: git: link to the gitdatamodel(7) tutorial
[3/4] doc: glossary: link four of the terms to gitdatamodel(7)
[4/4] doc: datamodel: link to the glossary

 Documentation/git.adoc              | 12 ++++++++----
 Documentation/gitdatamodel.adoc     |  4 ++++
 Documentation/gitglossary.adoc      |  1 +
 Documentation/glossary-content.adoc | 13 ++++++++++---
 command-list.txt                    |  1 +
 5 files changed, 24 insertions(+), 7 deletions(-)

Interdiff against v2:
diff --git a/Documentation/gitdatamodel.adoc b/Documentation/gitdatamodel.adoc
index d588630e633..56b7635c199 100644
--- a/Documentation/gitdatamodel.adoc
+++ b/Documentation/gitdatamodel.adoc
@@ -24,8 +24,6 @@ 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.
-
 [[objects]]
 OBJECTS
 -------
Range-diff against v2:
1:  35832098717 = 1:  35832098717 doc: git: list gitdatamodel(7) as a concept guide
2:  3d8c4334785 = 2:  3d8c4334785 doc: git: link to the gitdatamodel(7) tutorial
3:  04802040a8d = 3:  04802040a8d doc: glossary: link four of the terms to gitdatamodel(7)
4:  5e8911beb4e ! 4:  ef9469244f2 doc: datamodel: link to the glossary
    @@ Commit message
         Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
     
      ## Documentation/gitdatamodel.adoc ##
    -@@ Documentation/gitdatamodel.adoc: 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.
    -+
    - [[objects]]
    - OBJECTS
    - -------
     @@ Documentation/gitdatamodel.adoc: $ git reflog main --date=iso --no-decorate
      4ccb6d7 main@{2025-09-29 15:16:48 -0400}: commit (initial): Initial commit
      ----

base-commit: e9019fcafe0040228b8631c30f97ae1adb61bcdc
-- 
2.55.0.13.g335083658c8


  parent reply	other threads:[~2026-09-05 17:28 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
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 ` kristofferhaugsbakk [this message]
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=V3_CV_doc_datamodel_advertize.c7e@msgid.xyz \
    --to=kristofferhaugsbakk@fastmail.com \
    --cc=code@khaugsbakk.name \
    --cc=git@vger.kernel.org \
    --cc=julia@jvns.ca \
    --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