Git development
 help / color / mirror / Atom feed
From: Tuomas Ahola <taahol@utu.fi>
To: Junio C Hamano <gitster@pobox.com>
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: Wed, 11 Nov 2026 23:57:45 +0200	[thread overview]
Message-ID: <20261111215745.5LxQ4%taahol@utu.fi> (raw)
In-Reply-To: <xmqqh5hvt6ot.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> wrote:

> 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?
> 

AFAIK, yes.

  reply	other threads:[~2026-11-11 21:58 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
2026-11-11 21:57       ` Tuomas Ahola [this message]
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=20261111215745.5LxQ4%taahol@utu.fi \
    --to=taahol@utu.fi \
    --cc=code@khaugsbakk.name \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=julia@jvns.ca \
    --cc=peff@peff.net \
    --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