mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Chen-Yu Yeh <chenyou910331@gmail.com>
Cc: corbet@lwn.net, alexs@kernel.org, dzm91@hust.edu.cn,
	si.yanteng@linux.dev, srcres258@furdevs.cn,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/zh_TW: remove the unreachable plain-text translations
Date: Fri, 2 Oct 2026 14:44:32 +0800	[thread overview]
Message-ID: <ar9S0Oi7_G6uDJHO@wyuan.org> (raw)
In-Reply-To: <20260929131109.266535-1-chenyou910331@gmail.com>

On 2026-09-29 21:11:07 +0800, Chen-Yu Yeh <chenyou910331@gmail.com> wrote:

> These nine files predate the move of the documentation to
> reStructuredText.  Sphinx only reads .rst sources, so none of them is
> part of the built documentation, and nothing in the zh_TW tree refers to
> them; they can only be found by browsing the source tree.
> 
>   zh_TW file                          English original
>   IRQ.txt                             core-api/irq/index.rst
>   io_ordering.txt                     driver-api/io_ordering.rst
>   arch/arm/Booting                    arch/arm/booting.rst
>   arch/arm/kernel_user_helpers.txt    arch/arm/kernel_user_helpers.rst
>   arch/arm64/booting.txt              arch/arm64/booting.rst
>   arch/arm64/legacy_instructions.txt  arch/arm64/legacy_instructions.rst
>   arch/arm64/memory.txt               arch/arm64/memory.rst
>   arch/arm64/silicon-errata.txt       arch/arm64/silicon-errata.rst
>   arch/arm64/tagged-pointers.txt      arch/arm64/tagged-pointers.rst
> 
> Beyond the format, two of them no longer line up with the English tree
> at all: core-api/irq/index.rst is now only a toctree, the prose IRQ.txt
> translates having moved to core-api/irq/concepts.rst, and
> io_ordering.txt sits at the top level although its original lives under
> driver-api/.
> 
> As proposed in the zh_TW scope discussion and agreed there, remove them
> rather than convert them.  arch/arm/Booting was also listed in the
> proposal as a translation whose original had moved; being one of these
> files, it is removed rather than relocated.
> 
> Link: https://lore.kernel.org/linux-doc/CAKspUhJAbCWoxgh2eq8R5g_MiNK=oXgKPUWqGOpHh0w1-Fv74A@mail.gmail.com/
> Link: https://lore.kernel.org/linux-doc/ap5xEtMdwXS8Pvcf@wyuan.org/
> Signed-off-by: Chen-Yu Yeh <chenyou910331@gmail.com>
> ---
> This applies on top of v2 of the contact-block cleanup:
>   https://lore.kernel.org/linux-doc/20260929115956.229610-1-chenyou910331@gmail.com/
> 
> That series still edits IRQ.txt, io_ordering.txt and the arch/arm{,64}
> plain-text files (3/7 and 7/7) so that it stands on its own; once this
> patch lands those hunks are moot.  That also answers Jon's question on
> v1 7/7 about handling the old files together with the wider update:
> they are removed here instead.

So please don't forget to check the sequence when applying this. :)

Tested with 'make cleandocs && make htmldocs', no extra warnings caused.

Acked-by: Weijie Yuan <wy@wyuan.org>

Thanks.

      reply	other threads:[~2026-10-02  6:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 13:11 Chen-Yu Yeh
2026-10-02  6:44 ` Weijie Yuan [this message]

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=ar9S0Oi7_G6uDJHO@wyuan.org \
    --to=wy@wyuan.org \
    --cc=alexs@kernel.org \
    --cc=chenyou910331@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=si.yanteng@linux.dev \
    --cc=srcres258@furdevs.cn \
    /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

all inboxes | Powered by JetHome®