From: kristofferhaugsbakk@fastmail.com
To: git@vger.kernel.org
Cc: Kristoffer Haugsbakk <code@khaugsbakk.name>, Julia Evans <julia@jvns.ca>
Subject: [PATCH 0/4] doc: advertize gitdatamodel(1)
Date: Thu, 20 Aug 2026 20:55:20 +0200 [thread overview]
Message-ID: <CV_doc_datamodel_advertize.bea@msgid.xyz> (raw)
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Topic name: kh/doc-datamodel-advertize
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 datamodel page.
§ Testing
Other than the usual documentation testing, I was unsure if this would trip
any tests in the t/ directory which tests what output you get from `git
help --guides` or whatever else. So I merged today’s `seen` in in addition
to this topic and ran `cd t && make test`.
[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 | 6 ++++++
Documentation/gitglossary.adoc | 1 +
Documentation/glossary-content.adoc | 13 ++++++++++---
command-list.txt | 1 +
5 files changed, 26 insertions(+), 7 deletions(-)
base-commit: e9019fcafe0040228b8631c30f97ae1adb61bcdc
--
2.55.0.13.g85d2d65e389
next reply other threads:[~2026-08-20 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 18:55 kristofferhaugsbakk [this message]
2026-08-20 18:55 ` [PATCH 1/4] doc: git: list gitdatamodel(7) as a concept guide kristofferhaugsbakk
2026-08-20 18:55 ` [PATCH 2/4] doc: git: link to the gitdatamodel(7) tutorial kristofferhaugsbakk
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
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=CV_doc_datamodel_advertize.bea@msgid.xyz \
--to=kristofferhaugsbakk@fastmail.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=julia@jvns.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.