From: Junio C Hamano <gitster@pobox.com>
To: Tuomas Ahola <taahol@utu.fi>
Cc: <git@vger.kernel.org>, Julia Evans <julia@jvns.ca>,
Patrick Steinhardt <ps@pks.im>,
Kristoffer Haugsbakk <code@khaugsbakk.name>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH v3 1/2] command-list.txt: add gitformat-loose(5) and gitpacking(7)
Date: Thu, 05 Nov 2026 11:32:50 -0800 [thread overview]
Message-ID: <xmqqh5hvt6ot.fsf@gitster.g> (raw)
In-Reply-To: <20261029184834.2273-2-taahol@utu.fi> (Tuomas Ahola's message of "Thu, 29 Oct 2026 20:48:33 +0200")
Tuomas Ahola <taahol@utu.fi> writes:
> Three manpages from sections 5 and 7 are not featured in
> command-list.txt as concept guides or interface manuals.
>
> As easy fixes, add gitformat-loose(5) to 'developerinterfaces'
> and make gitpacking(7) a 'guide'.
>
> That leaves only gitweb.conf(5) which could be added to
> 'userinterfaces'. However, the manual would then appear
> as "web.conf" in `git help -a` which is just confusing.
> So, perhaps we are better off by leaving it out.
>
> Signed-off-by: Tuomas Ahola <taahol@utu.fi>
> ---
> command-list.txt | 2 ++
> 1 file changed, 2 insertions(+)
I agree we can decide what to do about gitweb. Is the list
otherwise complete to cover the available documents in .adoc format?
Thanks.
>
> diff --git a/command-list.txt b/command-list.txt
> index 5c649c882e..d96f56a379 100644
> --- a/command-list.txt
> +++ b/command-list.txt
> @@ -225,6 +225,7 @@ gitformat-bundle developerinterfaces
> gitformat-chunk developerinterfaces
> gitformat-commit-graph developerinterfaces
> gitformat-index developerinterfaces
> +gitformat-loose developerinterfaces
> gitformat-pack developerinterfaces
> gitformat-signature developerinterfaces
> gitglossary guide
> @@ -234,6 +235,7 @@ gitk mainporcelain
> gitmailmap userinterfaces
> gitmodules userinterfaces
> gitnamespaces guide
> +gitpacking guide
> gitprotocol-capabilities developerinterfaces
> gitprotocol-common developerinterfaces
> gitprotocol-http developerinterfaces
next prev parent reply other threads:[~2026-11-05 19:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 5:24 [PATCH 0/2] guides: keep Documentation/Makefile and command-list.txt in sync Tuomas Ahola
2026-09-09 5:25 ` [PATCH 1/2] command-list: add gitformat-loose(5) and gitpacking(7) Tuomas Ahola
2026-09-09 18:15 ` Junio C Hamano
2026-09-09 5:25 ` [PATCH 2/2] lint-docs: check the guide list in command-list.txt Tuomas Ahola
2026-09-09 18:15 ` Junio C Hamano
2026-09-10 19:43 ` [PATCH v2 0/2] guides: keep Documentation/Makefile and command-list.txt in sync Tuomas Ahola
2026-09-10 19:43 ` [PATCH v2 1/2] command-list.txt: add gitformat-loose(5) and gitpacking(7) Tuomas Ahola
2026-09-10 19:43 ` [PATCH v2 2/2] lint-docs: check the guide list in command-list.txt Tuomas Ahola
2026-10-29 18:48 ` [PATCH v3 0/2] guides: keep Documentation/Makefile and command-list.txt in sync Tuomas Ahola
2026-10-29 18:48 ` [PATCH v3 1/2] command-list.txt: add gitformat-loose(5) and gitpacking(7) Tuomas Ahola
2026-11-05 19:32 ` Junio C Hamano [this message]
2026-11-11 21:57 ` Tuomas Ahola
2026-10-29 18:48 ` [PATCH v3 2/2] lint-docs: check the guide list in command-list.txt Tuomas Ahola
2026-11-02 18:39 ` Julia Evans
2026-11-03 17:09 ` Tuomas Ahola
2026-11-05 19:41 ` Junio C Hamano
2026-11-11 22:00 ` Tuomas Ahola
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=xmqqh5hvt6ot.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=julia@jvns.ca \
--cc=peff@peff.net \
--cc=ps@pks.im \
--cc=taahol@utu.fi \
/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.