From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Julia Evans" <julia@jvns.ca>,
"Junio C Hamano" <gitster@pobox.com>,
GGGGGGGGGGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/3] [doc] Remove gittutorial-2
Date: Wed, 30 Sep 2026 16:07:03 +0200 [thread overview]
Message-ID: <7ef2e8a1-2890-4b45-8da1-2f9a04cf792d@app.fastmail.com> (raw)
In-Reply-To: <7ca55e6c-d12c-4105-b647-d76ed49d93ac@app.fastmail.com>
On Wed, Sep 30, 2026, at 15:16, Julia Evans wrote:
>> Sorry, but there was another. With this merged, doc-lint seems to
>> fail and breaks 'seen'.
>>
>> ...
>> LINT DOCSTYLE includes/cmd-config-section-all.adoc
>> no link: gittutorial-2
>> gmake[1]: *** [Makefile:537: lint-docs-manpages] Error 1
>> gmake[1]: Leaving directory
>> '/home/gitster/w/buildfarm/seen/Documentation'
>> gmake: *** [Makefile:4003: check-docs] Error 2
>
> Weird, when I run `make lint-docs` on my branch it succeeds
> (before merging it into `seen`). But I agree with you that
> it fails when merged into `seen`. I'll try to figure out why.
It looks like it’s because 4ce144a1 (lint-docs: check the guide list in
command-list.txt, 2026-09-10) introduced `MAN_GUIDES`.
diff --git Documentation/lint-manpages.sh Documentation/lint-manpages.sh
index a0ea572382d..d4a1977ba6b 100755
--- Documentation/lint-manpages.sh
+++ Documentation/lint-manpages.sh
@@ -1,21 +1,23 @@
[...]
check_missing_docs () (
ret=0
- for v in $ALL_COMMANDS
+ for v in $ALL_COMMANDS $MAN_GUIDES
do
next prev parent reply other threads:[~2026-09-30 14:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 20:25 [PATCH 0/3] [doc] Remove gittutorial-2 Julia Evans via GitGitGadget
2026-09-28 20:25 ` [PATCH 1/3] " Julia Evans via GitGitGadget
2026-09-28 20:25 ` [PATCH 2/3] [doc] Remove references to gittutorial-2 Julia Evans via GitGitGadget
2026-09-28 20:25 ` [PATCH 3/3] [doc] Delete translations of gittutorial-2 description Julia Evans via GitGitGadget
2026-09-29 7:50 ` [PATCH 0/3] [doc] Remove gittutorial-2 Junio C Hamano
2026-09-29 10:42 ` Julia Evans
2026-09-29 11:09 ` Julia Evans
2026-09-30 7:50 ` Junio C Hamano
2026-10-01 22:21 ` Julia Evans
2026-10-02 7:38 ` Junio C Hamano
2026-09-29 21:58 ` Junio C Hamano
2026-09-29 22:24 ` Junio C Hamano
2026-09-30 6:15 ` Tuomas Ahola
2026-09-30 14:22 ` Junio C Hamano
2026-09-30 13:16 ` Julia Evans
2026-09-30 14:07 ` Kristoffer Haugsbakk [this message]
2026-09-30 6:00 ` Tuomas Ahola
2026-09-30 14:01 ` Julia Evans
2026-10-05 20:20 ` [PATCH v2 0/2] " Julia Evans via GitGitGadget
2026-10-05 20:20 ` [PATCH v2 1/2] doc: remove gittutorial-2 Julia Evans via GitGitGadget
2026-10-05 20:37 ` Kristoffer Haugsbakk
2026-10-05 20:20 ` [PATCH v2 2/2] doc: remove references to gittutorial-2 Julia Evans via GitGitGadget
2026-10-05 20:37 ` [PATCH v2 0/2] [doc] Remove gittutorial-2 Junio C Hamano
2026-10-06 5:50 ` Tuomas Ahola
2026-10-06 17:17 ` Junio C Hamano
2026-10-06 18:45 ` Tuomas Ahola
2026-10-06 20:48 ` Junio C Hamano
2026-10-06 17:34 ` Julia Evans
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=7ef2e8a1-2890-4b45-8da1-2f9a04cf792d@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox