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 1/4] docs/zh_TW: move security-bugs to process/
Date: Fri, 2 Oct 2026 22:31:25 +0800	[thread overview]
Message-ID: <ar_APS7UG25kXXYH@wyuan.org> (raw)
In-Reply-To: <20260929131020.266120-2-chenyou910331@gmail.com>


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

> The English original moved from admin-guide/ to process/ in
> commit 44ac5abac86b ("Documentation/security-bugs: move from
> admin-guide/ to process/"), 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/admin-guide/security-bugs.rst

Yes, right.

> Move it to match the English layout, and list it under "Dealing with
> bugs" in process/index.rst as the English index does.  The content is
> unchanged; its :Original: reference already points at
> process/security-bugs and resolves the same way from the new location.

> The translation has only had mechanical changes since it was imported in
> 2021, and the English document did not change between that import and
> its move,

Hmm, is it? What does "mechanical changes" means? Does it mean small
changes like typos, format, and etc.?

Maybe I got it wrong, but I noticed that the current version has quite a
few new sections and additional content, though. Am I misunderstanding
something?

But I guess you might just have made a typing mistake here. The diff
below should be fine.

> so the move commit is the English version this translation mirrors.

That's right.

> It is also the oldest baseline the tool can use: checktransupdate.py
> does not follow renames, so a commit from before the move would make
> it fall back to comparing dates and report the file as up to date.

Right.

> update to commit 44ac5abac86b ("Documentation/security-bugs: move from
> admin-guide/ to process/")

Checked, and indeed. Current translation is aligned with 44ac5ab.

Thanks.

  reply	other threads:[~2026-10-02 14:31 UTC|newest]

Thread overview: 11+ 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 [this message]
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     ` 葉宸佑
2026-10-01 14:00       ` Jani Nikula
2026-10-02  3:44         ` 葉宸佑
2026-10-02 16:51     ` 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=ar_APS7UG25kXXYH@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®