Re: [PATCH 1/4] docs/zh_TW: move security-bugs to process/

[Weijie Yuan]

On 2026-10-03 17:56:02 +0800, 葉宸佑 <chenyou910331@xxxxxxxxx> 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@xxxxxxxxx> 於 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.