Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Tuomas Ahola <taahol@utu.fi>
Cc: Julia Evans via GitGitGadget <gitgitgadget@gmail.com>,
	<git@vger.kernel.org>,
	 Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	 Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH v2 0/2] [doc] Remove gittutorial-2
Date: Tue, 06 Oct 2026 10:17:22 -0700	[thread overview]
Message-ID: <xmqqfqyieokd.fsf@gitster.g> (raw)
In-Reply-To: <20261006055002.M9X9O%taahol@utu.fi> (Tuomas Ahola's message of "Tue, 6 Oct 2026 08:50:02 +0300")

Tuomas Ahola <taahol@utu.fi> writes:

>> Changes in v2:
>> 
>>  * Remove changes to .po files (thanks to Junio)
>>  * Reword commit messages to doc: ... (thanks to Tuomas)
>> 
>> To deal with the conflict with 4ce144a1 (which requires that all guides be
>> listed in command-list.txt) I think we need to add another exception to
>> lint-manpages.sh (like Tuomas said).
>> 
>
> Excluding the po/ stuff, the v1->v2 interdiff looks like this:
>
> $ git diff je/doc-remove-gittutorial-2@{1} je/doc-remove-gittutorial-2 -- ':!po/'
> diff --git a/command-list.txt b/command-list.txt
> index 5c649c882e..63ae2a67c9 100644
> --- a/command-list.txt
> +++ b/command-list.txt
> @@ -244,6 +244,7 @@ gitrepository-layout                    userinterfaces
>  gitrevisions                            userinterfaces
>  gitsubmodules                           guide
>  gittutorial                             guide
> +gittutorial-2                           guide
>  gitweb                                  ancillaryinterrogators
>  gitworkflows                            guide
>  scalar                                  mainporcelain
>
> That, as can be guessed, causes git(1) to advertize this "obsolete tutorial".
> Perhaps we would like to avoid that.
>
> $ (cd Documentation/ && ./doc-diff je/doc-remove-gittutorial-2@{1} je/doc-remove-gittutorial-2)
> diff --git a/7da429d7fb86fe400c48984ea1506a9e0477e80e/home/taahol/share/man/man1/git.1 b/0bf477ce01b45853195f5f3da63642712dc35579/home/taahol/share/man/man1/git.1
> index efc100186b..57a7f270c8 100644
> --- a/7da429d7fb86fe400c48984ea1506a9e0477e80e/home/taahol/share/man/man1/git.1
> +++ b/0bf477ce01b45853195f5f3da63642712dc35579/home/taahol/share/man/man1/git.1
> @@ -800,6 +800,9 @@ GUIDES
>         gittutorial(7)
>             A tutorial introduction to Git.
>  
> +       gittutorial-2(7)
> +           Obsolete tutorial.
> +
>         gitworkflows(7)
>             An overview of recommended workflows with Git.
>  
>
> And let's not worry about that exception you mentioned.  After this topic hits
> 'next', I can rebase mine on top on of this, and deal with all necessary
> integration work.

OK.  So ...

 - I'll tentatively eject both topics out of my tree,

 - Julia will send in a replacement that does not add gittutorial-2
   to the command-list, which will be merged to 'next',

 - and then your topic will be queued again with an evil merge (by
   me) to add gittutorial-2 back to the command-list file.

... and both topics will be happy?


  reply	other threads:[~2026-10-06 17:17 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
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 [this message]
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=xmqqfqyieokd.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=julia@jvns.ca \
    --cc=kristofferhaugsbakk@fastmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox