From: Jani Nikula <jani.nikula@linux.intel.com>
To: 葉宸佑 <chenyou910331@gmail.com>
Cc: corbet@lwn.net, alexs@kernel.org, dzm91@hust.edu.cn,
wy@wyuan.org, si.yanteng@linux.dev, srcres258@furdevs.cn,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [PATCH 4/4] docs/zh_TW: add missing :Original: fields
Date: Thu, 01 Oct 2026 17:00:23 +0300 [thread overview]
Message-ID: <22fdd310dfb0946bbe58ed71308e58d936cbed53@intel.com> (raw)
In-Reply-To: <CAKspUhKCpXGKb7zpz9MbtpixVMUWKXMJtK-z6CcrezGA6e+ETA@mail.gmail.com>
On Wed, 30 Sep 2026, 葉宸佑 <chenyou910331@gmail.com> wrote:
> You are right, and I should have seen it -- the rest of this series is
> built on that same expectation. checktransupdate.py also finds the
> original purely from the path, which is why 1/4-3/4 move the files
> rather than fix their :Original: fields. By the same token, at their old
> paths the language switcher cannot pair them with their originals
> either, which is a better argument for the moves than the one I gave.
Oh, by the way, I do think the series as a whole is worthwhile cleanup,
and having the :Original: fields is the current practice. Removing them
should be a separate change.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-10-01 14:00 UTC|newest]
Thread overview: 8+ 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-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 [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=22fdd310dfb0946bbe58ed71308e58d936cbed53@intel.com \
--to=jani.nikula@linux.intel.com \
--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 \
--cc=vegard.nossum@oracle.com \
--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®