Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Julia Evans via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Julia Evans <julia@jvns.ca>,
	Jiang Xin <worldhello.net@gmail.com>
Subject: Re: [PATCH 0/3] [doc] Remove gittutorial-2
Date: Tue, 29 Sep 2026 14:58:29 -0700	[thread overview]
Message-ID: <xmqqcxtven3u.fsf@gitster.g> (raw)
In-Reply-To: <pull.2241.git.1790627122.gitgitgadget@gmail.com> (Julia Evans via GitGitGadget's message of "Mon, 28 Sep 2026 20:25:19 +0000")

"Julia Evans via GitGitGadget" <gitgitgadget@gmail.com> writes:

>  Documentation/MyFirstObjectWalk.adoc |   2 +-
>  Documentation/git.adoc               |   2 +-
>  Documentation/gitcore-tutorial.adoc  |   1 -
>  Documentation/gitcvs-migration.adoc  |   2 +-
>  Documentation/gitglossary.adoc       |   1 -
>  Documentation/gittutorial-2.adoc     | 422 +--------------------------
>  Documentation/gittutorial.adoc       |  23 +-
>  command-list.txt                     |   1 -
>  po/bg.po                             |   3 -
>  po/ca.po                             |   4 -
>  po/de.po                             |   3 -
>  po/el.po                             |   4 -
>  po/es.po                             |   3 -
>  po/fr.po                             |   3 -
>  po/ga.po                             |   3 -
>  po/id.po                             |   3 -
>  po/it.po                             |   4 -
>  po/ko.po                             |   3 -
>  po/pl.po                             |   3 -
>  po/pt_PT.po                          |   4 -
>  po/ru.po                             |   3 -
>  po/sv.po                             |   3 -
>  po/tr.po                             |   3 -
>  po/uk.po                             |   3 -
>  po/vi.po                             |   3 -
>  po/zh_CN.po                          |   4 -
>  po/zh_TW.po                          |   4 -
>  27 files changed, 14 insertions(+), 503 deletions(-)

One thing I forgot to mention.

I think we try to stay out of the po/ directory unless the patch is
about updating translated text to catch up with translatable text
that was updated by code or doc changes.  IOW, unless you are
working on the patch set as a member of the l10n team, you do not
touch these files.  This is to avoid unnecessary churn and
burdening the l10n teams with synchronization pain.

The above is my understanding of the workflow agreed on by people
inside and outside the l10n group, but I'd like to double-check
with the i18n coordinator (Cc'ed).  If I understand correctly, the
recent workflow used by the l10n teams gives more autonomy to
individual teams than before, which may have changed the equation.

The removals we see in the diffstat touch lines in the early part
that appears in the manual page, namely ...

    gittutorial-2(7)
    ================

    NAME
    ----
    gittutorial-2 - A tutorial introduction to Git: part two

    SYNOPSIS

the string used for "NAME", and one of them looks like this:

        diff --git c/po/es.po w/po/es.po
        index aa1bb9bf90..dcdcbf5360 100644
        --- c/po/es.po
        +++ w/po/es.po
        @@ -14046,9 +14046,6 @@ msgstr "Montar un repositorio dentro de otro"
         msgid "A tutorial introduction to Git"
         msgstr "Un tutorial de introducción a Git"
        -msgid "A tutorial introduction to Git: part two"
        -msgstr "Un tutorial de introducción a Git: parte dos"
        -
         msgid "Git web interface (web frontend to Git repositories)"
         msgstr "Interfaz web Git (interfaz web para repositorios Git)"

I'd say a patch set like this one, which is not about updating the
localization, should just leave po/ intact, since the removal does
not help without a corresponding addition from the same "NAME" in the
file that replaces this "gittutorial-2", which reads like

    gittutorial-2(7)
    ================

    NAME
    ----
    gittutorial-2 - Obsolete tutorial

    SYNOPSIS

and as the patch set stands, we are leaving it to the l10n teams
anyway to add "Obsolete tutorial" to the set of translatable
strings.

Jiang Xin (i18n/l10n coordinator), what do you and the l10n teams
want to see in a patch like this one?

Thanks.

  parent reply	other threads:[~2026-09-29 21:58 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 [this message]
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
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=xmqqcxtven3u.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=julia@jvns.ca \
    --cc=worldhello.net@gmail.com \
    /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