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

Weijie Yuan <[email protected]>
Newsgroups org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
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 <[email protected]>

> Signed-off-by: Chen-Yu Yeh <[email protected]>
> ---
>  .../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. ;-)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.