Re: [PATCH v2 01/16] docs/zh_TW: process: localize terminology in 7.AdvancedTopics.rst

[葉宸佑]

> A small gripe: what is the best practice for reviewing a new revision
> of a patch series after it has been rerolled?

Sorry about that -- a 16-patch Chinese series is about the worst case
for this, and it is my problem to make easier, not yours.

For v3 I will use "git format-patch --range-diff=<v2-tag>", which puts
a per-patch range-diff in the cover letter. That should at least show
you which patches actually changed and how, without you having to
reconstruct it.

Longer term this feels like something the zh_TW how-to should cover:
how to send and review Chinese translation series specifically. I have
been collecting notes while doing this one (line-width handling for
CJK, why checkpatch miscounts Chinese lines, the reflow pitfalls) and
would be happy to draft that section once this series lands.

Weijie Yuan <wy@xxxxxxxxx> 於 2026年7月30日週四 上午12:09寫道：
>
> On Tue, Jul 28, 2026 at 05:10:23PM +0800, Chen-Yu Yeh wrote:
> > Localize mainland terms to Taiwanese Mandarin (內核→核心, 軟件→軟體,
> > 高級→進階, 項目→專案, 用戶→使用者, ...) and sync with the English
> > original (Github → GitHub).
> >
> > update to commit 5ce70894f6ca ("Doc: correct spelling and wording
> > mistakes")
>
> Reviewed-by: Weijie Yuan <wy@xxxxxxxxx>
>
> > Signed-off-by: Chen-Yu Yeh <chenyou910331@xxxxxxxxx>
> > ---
> >  .../zh_TW/process/7.AdvancedTopics.rst        | 110 +++++++++---------
> >  1 file changed, 56 insertions(+), 54 deletions(-)
>
> A small gripe: what is the best practice for reviewing a new revision of
> a patch series after it has been rerolled?
>
> For this series, I found the output of b4 diff rather difficult to read,
> so I had to split out the individual patches and inspect them using git
> mailinfo and interdiff. That, however, means losing the built-in
> highlighting provided by b4 diff.
>
> In this case, I would say a range-diff/interdiff for each patch seems to
> be a good solution in general, while obviously that's not that
> convenient for the patch sender.
>
> Perhaps there is no best solution to this problem; Git may simply not be
> expected to handle Chinese text particularly well.
>
> I would appreciate it if some one more experienced could give me some
> tips. But this series is however quite special. Usually we won't meet a
> large series which contains many diffs in it like this.
>
> Then I suppose we'll just have to ride out these growing pains. ;-)