All of lore.kernel.org
 help / color / mirror / Atom feed
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 2/4] docs/zh_TW: move magic-number to staging/
Date: Tue, 29 Sep 2026 21:10:16 +0800	[thread overview]
Message-ID: <20260929131020.266120-3-chenyou910331@gmail.com> (raw)
In-Reply-To: <20260929131020.266120-1-chenyou910331@gmail.com>

The English original moved from process/ to staging/ in
commit f9a4f4a0e1f5 ("Docs: Move magic-number from process to staging"),
but the translation stayed behind.  checktransupdate.py locates the
English original from the translation's path, so it currently reports:

  Cannot find the origin path for
  Documentation/translations/zh_TW/process/magic-number.rst

Move it to match the English layout.  zh_TW has no staging/ directory
yet, so add a staging/index.rst that follows the English one, listing
the documents not translated yet under TODOList as zh_CN does, and link
it from the top-level index in place of its TODOList entry.  The content
of magic-number.rst is unchanged.

Unlike most of the tree, this translation was kept in step for a while
by the English authors themselves: the 2022 series that removed stale
magic numbers edited the translations as well, and so did
commit dd8d4bc28ad7 ("net: remove ax25 and amateur radio (hamradio)
subsystem").  The one English change it lacks is
commit cdcfc029482a ("Documentation: Fix incorrect paths/magic in magic
numbers rst"), which went in after the move.  Use the move commit as the
baseline so that change is reported; checktransupdate.py will also list
dd8d4bc28ad7, which is already reflected here.

update to commit f9a4f4a0e1f5 ("Docs: Move magic-number from process to
staging")

Signed-off-by: Chen-Yu Yeh <chenyou910331@gmail.com>
---
 Documentation/translations/zh_TW/index.rst    |  5 ++--
 .../translations/zh_TW/process/index.rst      |  5 ----
 .../translations/zh_TW/staging/index.rst      | 23 +++++++++++++++++++
 .../{process => staging}/magic-number.rst     |  0
 4 files changed, 26 insertions(+), 7 deletions(-)
 create mode 100644 Documentation/translations/zh_TW/staging/index.rst
 rename Documentation/translations/zh_TW/{process => staging}/magic-number.rst (100%)

diff --git a/Documentation/translations/zh_TW/index.rst b/Documentation/translations/zh_TW/index.rst
index fb86de03c423..1dddf5963864 100644
--- a/Documentation/translations/zh_TW/index.rst
+++ b/Documentation/translations/zh_TW/index.rst
@@ -112,9 +112,10 @@ TODOList:
 有幾份未分類的文檔似乎不適合放在文檔的其他部分,或者可能需要進行一些調整和/或
 轉換爲reStructureText格式,也有可能太舊。
 
-TODOList:
+.. toctree::
+   :maxdepth: 2
 
-* staging/index
+   staging/index
 
 術語表
 ------
diff --git a/Documentation/translations/zh_TW/process/index.rst b/Documentation/translations/zh_TW/process/index.rst
index 18653aa75d7d..de99156324df 100644
--- a/Documentation/translations/zh_TW/process/index.rst
+++ b/Documentation/translations/zh_TW/process/index.rst
@@ -113,11 +113,6 @@ TODOList:
 
 這裡是一些大多數開發者會感興趣的其他社群指南:
 
-.. toctree::
-   :maxdepth: 1
-
-   magic-number
-
 TODOList:
 
 * kernel-docs
diff --git a/Documentation/translations/zh_TW/staging/index.rst b/Documentation/translations/zh_TW/staging/index.rst
new file mode 100644
index 000000000000..556c63a17f9c
--- /dev/null
+++ b/Documentation/translations/zh_TW/staging/index.rst
@@ -0,0 +1,23 @@
+.. SPDX-License-Identifier: GPL-2.0
+
+.. include:: ../disclaimer-zh_TW.rst
+
+:Original: Documentation/staging/index.rst
+
+未分類文件
+==========
+
+.. toctree::
+   :maxdepth: 2
+
+   magic-number
+
+TODOList:
+
+* crc32
+* lzo
+* remoteproc
+* rpmsg
+* speculation
+* static-keys
+* xz
diff --git a/Documentation/translations/zh_TW/process/magic-number.rst b/Documentation/translations/zh_TW/staging/magic-number.rst
similarity index 100%
rename from Documentation/translations/zh_TW/process/magic-number.rst
rename to Documentation/translations/zh_TW/staging/magic-number.rst
-- 
2.43.0


  parent reply	other threads:[~2026-09-29 13:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 13:10 [PATCH 0/4] docs/zh_TW: relocate translations to follow the English layout Chen-Yu Yeh
2026-09-29 13:10 ` [PATCH 1/4] docs/zh_TW: move security-bugs to process/ Chen-Yu Yeh
2026-10-02 14:31   ` Weijie Yuan
2026-10-03  9:53     ` 葉宸佑
2026-10-03  9:56       ` 葉宸佑
2026-10-03 10:02         ` Weijie Yuan
2026-09-29 13:10 ` Chen-Yu Yeh [this message]
2026-10-03  4:08   ` [PATCH 2/4] docs/zh_TW: move magic-number to staging/ Weijie Yuan
2026-09-29 13:10 ` [PATCH 3/4] docs/zh_TW: move gdb-kernel-debugging to process/debugging/ Chen-Yu Yeh
2026-10-03  4:19   ` Weijie Yuan
2026-10-03 10:22     ` 葉宸佑
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     ` 葉宸佑
2026-10-01 14:00       ` Jani Nikula
2026-10-02  3:44         ` 葉宸佑
2026-10-02 16:51     ` Weijie Yuan
2026-10-03  4:22   ` Weijie Yuan

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-3-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.