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

[PATCH v3 3/4] doc: glossary: link four of the terms to gitdatamodel(7)

From
Kkristofferhaugsbakk@fastmail.com <kristofferhaugsbakk@fastmail.com>
Date
Sep 5, 2026, 17:28 UTC
Message-ID
<V3_glossary_4_terms_datam.c81@msgid.xyz>
In-Reply-To
<V3_CV_doc_datamodel_advertize.c7e@msgid.xyz>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>

Four of the terms in the glossary are discussed in gitdatamodel(7). Let’s link to the data model page from the glossary.

The phrasing needs to be tweaked based on what gitdatamodel(7) offers for each term compared to the glossary, or even other pages (see the git-reflog(1) mention). For instance, the ref/reference discussion can be called a “see also” since the glossary here already goes into detail. On the other hand, gitdatamodel(7) offers more details on the subject of “the index”.

Let’s also add gitdatamodel(7) to See Also. It is at least as relevant as the other tutorial pages that are already mentioned.

Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
Notes (series):
    v2:
    No changes.
    
    I reread the Ref entry in the glossary and compared it to the
    Reference entry on the data model page. These two texts cover
    similar things (except the “irregular refs”, only covered in the
    glossary). The data model page is slightly more conceptual in tone.
    
    That’s why I originally went with just “see also” instead of for
    example “see also ... more details” or “see also ... for a more
    conceptual overview). They are too similar to distinguish further
    in this context.
 Documentation/gitglossary.adoc      |  1 +
 Documentation/glossary-content.adoc | 13 ++++++++++---
 2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/Documentation/gitglossary.adoc b/Documentation/gitglossary.adoc
index 0e85be48470..b046d9cb293 100644
--- a/Documentation/gitglossary.adoc
+++ b/Documentation/gitglossary.adoc
@@ -16,6 +16,7 @@ include::glossary-content.adoc[]
 
 SEE ALSO
 --------
+linkgit:gitdatamodel[7],
 linkgit:gittutorial[7],
 linkgit:gittutorial-2[7],
 linkgit:gitcvs-migration[7],
diff --git a/Documentation/glossary-content.adoc b/Documentation/glossary-content.adoc
index 8c4e9dd3bee..52301a56dda 100644
--- a/Documentation/glossary-content.adoc
+++ b/Documentation/glossary-content.adoc
@@ -251,7 +251,8 @@ for a more flexible and robust system to do the same thing.
 	as objects. The index is a stored version of your
 	<<def_working_tree,working tree>>. Truth be told, it can also contain a second, and even
 	a third version of a working tree, which are used
-	when <<def_merge,merging>>.
+	when <<def_merge,merging>>. See "THE INDEX" in
+	linkgit:gitdatamodel[7] for details.
 
 [[def_index_entry]]index entry::
 	The information regarding a particular file, stored in the
@@ -290,7 +291,8 @@ This commit is referred to as a "merge commit", or sometimes just a
 [[def_object]]object::
 	The unit of storage in Git. It is uniquely identified by the
 	<<def_SHA1,SHA-1>> of its contents. Consequently, an
-	object cannot be changed.
+	object cannot be changed. See "OBJECTS" in
+	linkgit:gitdatamodel[7] for details.
 
 [[def_object_database]]object database::
 	Stores a set of "objects", and an individual <<def_object,object>> is
@@ -587,12 +589,17 @@ extended in the future:
 Different subhierarchies are used for different purposes. For example,
 the `refs/heads/` hierarchy is used to represent local branches whereas
 the `refs/tags/` hierarchy is used to represent local tags..
++
+See also "REFERENCES" in linkgit:gitdatamodel[7].
 
 [[def_reflog]]reflog::
 	A reflog shows the local "history" of a ref.  In other words,
 	it can tell you what the 3rd last revision in _this_ repository
 	was, and what was the current state in _this_ repository,
-	yesterday 9:14pm.  See linkgit:git-reflog[1] for details.
+	yesterday 9:14pm.
++
+See "REFLOGS" in linkgit:gitdatamodel[7] for a short explanation of the
+format. See linkgit:git-reflog[1] for details.
 
 [[def_refspec]]refspec::
 	A "refspec" is used by <<def_fetch,fetch>> and
-- 
2.55.0.13.g335083658c8
Previous: kristofferhaugsbakk@fastmail.comNext: kristofferhaugsbakk@fastmail.com
Message 22 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.