From: Tuomas Ahola <taahol@utu.fi>
To: Julia Evans <julia@jvns.ca>
Cc: <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
Patrick Steinhardt <ps@pks.im>,
Kristoffer Haugsbakk <code@khaugsbakk.name>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH v3 2/2] lint-docs: check the guide list in command-list.txt
Date: Tue, 3 Nov 2026 19:09:44 +0200 [thread overview]
Message-ID: <20261103170944.kmZMv%taahol@utu.fi> (raw)
In-Reply-To: <48aa1e9a-3049-4316-9054-644a8754b0dd@app.fastmail.com>
"Julia Evans" <julia@jvns.ca> wrote:
> On Thu, Oct 29, 2026, at 2:48 PM, Tuomas Ahola wrote:
> > diff --git a/Documentation/lint-manpages.sh b/Documentation/lint-manpages.sh
> > index a0ea572382..31ee3cbe72 100755
> > --- a/Documentation/lint-manpages.sh
> > +++ b/Documentation/lint-manpages.sh
> > @@ -1,21 +1,23 @@
> > #!/bin/sh
> >
> > extract_variable () {
> > + file="${2:-../Makefile}"
>
> I think what's happening here is that previously we were
> getting the variables from ./Makefile (in the basedir), but now we need
> some variables from ./Makefile and some from Documentation/Makefile.
>
> Would it make sense to get all the variables from Documentation/Makefile?
>
If that's possible, then sure, why not. But I think we are mostly extracting
from the top-level Makefile such information that simply isn't available in the
docs Makefile (and vice versa)?
> > + directory="$(dirname "$file")"
> > (
> > - cat ../Makefile
> > + cat "$file"
> > cat <<EOF
> > print_variable:
> > @\$(foreach b,\$($1),echo XXX \$(b:\$X=) YYY;)
> > EOF
> > ) |
> > - make -C .. -f - print_variable 2>/dev/null |
> > + make -C "$directory" -f - print_variable 2>/dev/null |
> > sed -n -e 's/.*XXX \(.*\) YYY.*/\1/p'
> > }
> >
> > check_missing_docs () (
> > ret=0
> >
> > - for v in $ALL_COMMANDS
> > + for v in $ALL_COMMANDS $MAN_GUIDES
> > do
> > case "$v" in
> > git-merge-octopus) continue;;
> > @@ -29,6 +31,8 @@ check_missing_docs () (
> > git-stage) continue;;
> > git-legacy-*) continue;;
> > git-?*--?* ) continue ;;
> > + gittutorial-2) continue ;;
> > + gitweb.conf) continue ;;
> > esac
> >
> > if ! test -f "$v.adoc"
> > @@ -87,6 +91,7 @@ check_extraneous_docs () {
> > BUILT_INS="$(extract_variable BUILT_INS)"
> > ALL_COMMANDS="$(extract_variable ALL_COMMANDS)"
> > EXCLUDED_PROGRAMS="$(extract_variable EXCLUDED_PROGRAMS)"
> > +MAN_GUIDES="$(extract_variable MAN_GUIDES ./Makefile)"
> >
> > findings=$(
> > if ! check_missing_docs
> > --
> > ta/command-list-guides-sync-lint
next prev parent reply other threads:[~2026-11-03 17:10 UTC|newest]
Thread overview: 15+ 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-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 [this message]
2026-11-05 19:41 ` Junio C Hamano
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=20261103170944.kmZMv%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