From: Weijie Yuan <wy@wyuan.org>
To: 葉宸佑 <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: Sat, 3 Oct 2026 18:02:58 +0800 [thread overview]
Message-ID: <asDS0rS9Racqp3B6@wyuan.org> (raw)
In-Reply-To: <CAKspUh+XM_E0CyrG8Lf-fGNFuQop0+i5_O7b+eRJ_Ghp0x6JZw@mail.gmail.com>
On 2026-10-03 17:56:02 +0800, 葉宸佑 <chenyou910331@gmail.com> wrote:
> On Sat, Oct 03, 2026, Chen-Yu Yeh wrote:
> > The <N> commits since the move, including the new sections you noticed,
>
> That should read 17 -- I left a placeholder in. Sorry for the noise.
>
> Chen-Yu
>
> 葉宸佑 <chenyou910331@gmail.com> 於 2026年10月3日週六 下午5:53寫道:
> >
> > On Fri, Oct 02, 2026 at 10:31:25PM +0800, Weijie Yuan wrote:
> > > > 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.?
> >
> > Yes -- changes that did not touch the translated text itself: the
> > address updates in 2023, the tree-wide character conversion, and the
> > path updates that came with the English move.
Yup.
> >
> > > 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?
> >
> > Those all went in after the move. The window I meant is from the import
> > (July 2021) to the move (March 2023), and the English file has no
> > commits in it:
> >
> > $ git log --oneline --since=2021-07-29 --until=2023-03-05 -- \
> > Documentation/admin-guide/security-bugs.rst
> > $
> >
> > The <N> commits since the move, including the new sections you noticed,
> > are exactly what checktransupdate.py reports against the 44ac5abac86b
> > baseline once this is applied. That is the point of the move: the
> > backlog becomes visible instead of "Cannot find the origin path".
> >
> > I should have written "between the import and the move" more plainly;
> > as it stands it is easy to read as "since the import".
;) Yes, this made me take a closer look.
Thanks for the detailed explanation. So this is just a nitpick which
does not matter much.
Thanks.
next prev parent reply other threads:[~2026-10-03 10:04 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 [this message]
2026-09-29 13:10 ` [PATCH 2/4] docs/zh_TW: move magic-number to staging/ Chen-Yu Yeh
2026-10-03 4:08 ` 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=asDS0rS9Racqp3B6@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 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.