From: Chen-Yu Yeh <chenyou910331@gmail.com>
To: corbet@lwn.net, alexs@kernel.org
Cc: dzm91@hust.edu.cn, wy@wyuan.org, si.yanteng@linux.dev,
srcres258@furdevs.cn, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chen-Yu Yeh <chenyou910331@gmail.com>
Subject: [PATCH 0/4] docs/zh_TW: relocate translations to follow the English layout
Date: Tue, 29 Sep 2026 21:10:14 +0800 [thread overview]
Message-ID: <20260929131020.266120-1-chenyou910331@gmail.com> (raw)
Three zh_TW translations still sit where their English originals used
to live, so tools/docs/checktransupdate.py cannot find the originals at
all. This series moves them, gives each a baseline, and adds the
:Original: fields that were missing, as proposed in the zh_TW scope
discussion:
https://lore.kernel.org/linux-doc/CAKspUhJAbCWoxgh2eq8R5g_MiNK=oXgKPUWqGOpHh0w1-Fv74A@mail.gmail.com/
translation moves to baseline
admin-guide/security-bugs process/security-bugs 44ac5abac86b
process/magic-number staging/magic-number f9a4f4a0e1f5
dev-tools/gdb-kernel-... process/debugging/gdb-kernel-.. d5af79c05e93
Each baseline is the English move commit. checktransupdate.py does not
follow renames, so a commit from before a move is invisible at the new
path and the tool silently falls back to reporting the file as current;
the move commit is the oldest baseline it can use. Where that hides a
missing change, the commit message records it (6b219431037b for
gdb-kernel-debugging).
Two side effects of the tool reading one "update to commit" line per
commit, which this series does not try to paper over:
- process/index.rst is touched by the moves and so inherits their
baseline; the tool now lists five English index commits that the
recent process series already applied.
- staging/index.rst and process/debugging/index.rst are new; the latter
is listed against a592a36e4937, which only drops the index-link
boilerplate that translations keep anyway.
The fourth relocation named in the proposal, arch/arm/Booting, is one of
the unreachable plain-text files and is removed in a separate series
instead.
This applies on top of v2 of the contact-block cleanup:
https://lore.kernel.org/linux-doc/20260929115956.229610-1-chenyou910331@gmail.com/
Chen-Yu Yeh (4):
docs/zh_TW: move security-bugs to process/
docs/zh_TW: move magic-number to staging/
docs/zh_TW: move gdb-kernel-debugging to process/debugging/
docs/zh_TW: add missing :Original: fields
.../zh_TW/admin-guide/clearing-warn-once.rst | 2 +
.../zh_TW/admin-guide/cpu-load.rst | 2 +
.../translations/zh_TW/admin-guide/index.rst | 1 -
.../translations/zh_TW/arch/index.rst | 2 +
.../translations/zh_TW/dev-tools/index.rst | 1 -
.../translations/zh_TW/dev-tools/sparse.rst | 4 +-
Documentation/translations/zh_TW/index.rst | 5 +-
.../debugging}/gdb-kernel-debugging.rst | 2 +-
.../zh_TW/process/debugging/index.rst | 70 +++++++++++++++++++
.../translations/zh_TW/process/index.rst | 9 +--
.../security-bugs.rst | 0
.../translations/zh_TW/staging/index.rst | 23 ++++++
.../{process => staging}/magic-number.rst | 0
13 files changed, 108 insertions(+), 13 deletions(-)
rename Documentation/translations/zh_TW/{dev-tools => process/debugging}/gdb-kernel-debugging.rst (99%)
create mode 100644 Documentation/translations/zh_TW/process/debugging/index.rst
rename Documentation/translations/zh_TW/{admin-guide => process}/security-bugs.rst (100%)
create mode 100644 Documentation/translations/zh_TW/staging/index.rst
rename Documentation/translations/zh_TW/{process => staging}/magic-number.rst (100%)
--
2.43.0
next reply other threads:[~2026-09-29 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 13:10 Chen-Yu Yeh [this message]
2026-09-29 13:10 ` [PATCH 1/4] docs/zh_TW: move security-bugs to process/ Chen-Yu Yeh
2026-09-29 13:10 ` [PATCH 2/4] docs/zh_TW: move magic-number to staging/ Chen-Yu Yeh
2026-09-29 13:10 ` [PATCH 3/4] docs/zh_TW: move gdb-kernel-debugging to process/debugging/ Chen-Yu Yeh
2026-09-29 13:10 ` [PATCH 4/4] docs/zh_TW: add missing :Original: fields Chen-Yu Yeh
2026-09-29 14:40 ` Jani Nikula
2026-09-30 12:49 ` 葉宸佑
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=20260929131020.266120-1-chenyou910331@gmail.com \
--to=chenyou910331@gmail.com \
--cc=alexs@kernel.org \
--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 \
--cc=wy@wyuan.org \
/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®