Git development
 help / color / mirror / Atom feed
From: Tuomas Ahola <taahol@utu.fi>
To: Junio C Hamano <gitster@pobox.com>
Cc: Julia Evans via GitGitGadget <gitgitgadget@gmail.com>,
	<git@vger.kernel.org>, Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH 0/3] [doc] Remove gittutorial-2
Date: Wed, 30 Sep 2026 09:15:24 +0300	[thread overview]
Message-ID: <20260930061524.GNkIK%taahol@utu.fi> (raw)
In-Reply-To: <xmqq8q4jelvp.fsf@gitster.g>

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

> Junio C Hamano <gitster@pobox.com> writes:
> 
> >
> > One thing I forgot to mention.
> 
> 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
> 

If we want to build gittutorial-2(7) as a manpage stub but to hide it in `git
help --guides`, we can squelch that linter error with a merge-fix:

diff --git a/Documentation/lint-manpages.sh b/Documentation/lint-manpages.sh
index d4a1977ba6..db2a54116d 100755
--- a/Documentation/lint-manpages.sh
+++ b/Documentation/lint-manpages.sh
@@ -32,6 +32,7 @@ check_missing_docs () (
 		git-legacy-*) continue;;
 		git-?*--?* ) continue ;;
 		gitweb.conf) continue ;;
+		gittutorial-2) continue ;;
 		esac
 
 		if ! test -f "$v.adoc"

  reply	other threads:[~2026-09-30  6:15 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 [this message]
2026-09-30 14:22       ` Junio C Hamano
2026-09-30 13:16     ` Julia Evans
2026-09-30 14:07       ` Kristoffer Haugsbakk
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=20260930061524.GNkIK%taahol@utu.fi \
    --to=taahol@utu.fi \
    --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