All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: kristofferhaugsbakk@fastmail.com
Cc: git@vger.kernel.org, Kristoffer Haugsbakk <code@khaugsbakk.name>,
	Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH 1/4] doc: git: list gitdatamodel(7) as a concept guide
Date: Fri, 21 Aug 2026 14:22:40 +0200	[thread overview]
Message-ID: <aohDEKEs82MaWECV@pks.im> (raw)
In-Reply-To: <git_help_--guide_datam.beb@msgid.xyz>

On Thu, Aug 20, 2026 at 08:55:21PM +0200, kristofferhaugsbakk@fastmail.com wrote:
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
> 
> dee80940 (doc: add an explanation of Git's data model, 2025-11-12) added
> gitdatamodel(7), documenting Git’s data model. But it is not mentioned
> everywhere.

Nit: s/everywhere/anywhere?

> diff --git a/command-list.txt b/command-list.txt
> index 21b802c4202..63ae2a67c94 100644
> --- a/command-list.txt
> +++ b/command-list.txt
> @@ -217,6 +217,7 @@ gitcli                                  userinterfaces
>  gitcore-tutorial                        guide
>  gitcredentials                          guide
>  gitcvs-migration                        guide
> +gitdatamodel                            guide
>  gitdiffcore                             guide
>  giteveryday                             guide
>  gitfaq                                  guide

Makes sense.

Patrick

  reply	other threads:[~2026-08-21 12:22 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 [this message]
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 ` [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=aohDEKEs82MaWECV@pks.im \
    --to=ps@pks.im \
    --cc=code@khaugsbakk.name \
    --cc=git@vger.kernel.org \
    --cc=julia@jvns.ca \
    --cc=kristofferhaugsbakk@fastmail.com \
    /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.