From: Yukai Wu <xiaoyewuz.ruster@gmail.com>
To: Weijie Yuan <wy@wyuan.org>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Jonathan Corbet <corbet@lwn.net>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Dongliang Mu <dzm91@hust.edu.cn>,
Shuah Khan <skhan@linuxfoundation.org>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org,
Chen-Yu Yeh <chenyou910331@gmail.com>
Subject: Re: [PATCH] docs/zh_CN: Update arch/riscv/vm-layout.rst translation
Date: Sun, 30 Aug 2026 09:33:12 +0800 [thread overview]
Message-ID: <f-IgWNAyTmaoW34tfNxIvg@gmail.com> (raw)
In-Reply-To: <apL7ctZhcN5t77Yu@wyuan.org>
On Saturday, August 29, 2026 11:32:02 PM China Standard Time Weijie Yuan
wrote:
> Hi, it's me again ;-)
>
> On Sat, Aug 29, 2026 at 12:15:10PM +0800, Yukai Wu wrote:
> > Update Documentation/arch/riscv/vm-layout.rst translation.
> >
> > Update the translation through commit 954260ff5a46
> > ("Revert "RISC-V: mm: Document mmap changes"")
>
> Somehow I guess you didn't get the actual meaning behind this "Update xxx
> through commit...".
>
> Correct me if I'm wrong. If you write this line in your commit message.
> Then it means if we apply this patch of yours. The Chinese documentation
> of this file should be already _completely_ synchronized.
>
I agree. My fault again.
> However, the current translation of this file is missing this part:
>
> RISC-V Linux Kernel SV57
> ------------------------
>
> ... which is not translated/synchronized in your patch.
>
>
Didn't see that because I just used the tools/docs/checktransupdate.py script,
which cannot see the commits before ed843ae947f8 ("docs: move riscv under
arch"). That commit just moved the Chinese translation but was treated as an
update by the script. And I only looked at the commits reported by the script.
> Note that I'm not blaming on you for this. But I feel this is a point
> that a newcomer might find confusing, including me and Chen-Yu a couple
> of weeks ago, if did not read the script.
>
> Our current how-to.rst only asks to write this line in the commit
> message but does not explain the results or the actual work behind it.
>
> [...]
> Update the translation through commit b080e52110ea
> ("docs: update self-protection __ro_after_init status")
> # 请执行 git log --oneline <您翻译的英文文档路径>,并替换上述内容
>
> So when a newcomer comes and just does what this asks, without
> considering whether his/her/its translation is completely
> synchronized or not, our script would be kind of inaccurate. ?
>
> Maybe we can add a description or a hint like:
>
> If your current changes make the translation completely in line with the
> English version, then please add this line after your descriptions and
> before a blank line and your sign-off:
>
> Update the translation through commit e83c5163316f
> (Initial revision of "git", the information manager from hell)
>
> ..then follows a template commit message
Allowing partial updates to the translation?
>
>
> Any ideas?
>
> (Should I cc the original authors of the script?)
CC the authors of the checktransupdate.py script?
>
> Thanks.
Best,
Yukai Wu
WARNING: multiple messages have this Message-ID (diff)
From: Yukai Wu <xiaoyewuz.ruster@gmail.com>
To: Weijie Yuan <wy@wyuan.org>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Jonathan Corbet <corbet@lwn.net>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Dongliang Mu <dzm91@hust.edu.cn>,
Shuah Khan <skhan@linuxfoundation.org>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org,
Chen-Yu Yeh <chenyou910331@gmail.com>
Subject: Re: [PATCH] docs/zh_CN: Update arch/riscv/vm-layout.rst translation
Date: Sun, 30 Aug 2026 09:33:12 +0800 [thread overview]
Message-ID: <f-IgWNAyTmaoW34tfNxIvg@gmail.com> (raw)
In-Reply-To: <apL7ctZhcN5t77Yu@wyuan.org>
On Saturday, August 29, 2026 11:32:02 PM China Standard Time Weijie Yuan
wrote:
> Hi, it's me again ;-)
>
> On Sat, Aug 29, 2026 at 12:15:10PM +0800, Yukai Wu wrote:
> > Update Documentation/arch/riscv/vm-layout.rst translation.
> >
> > Update the translation through commit 954260ff5a46
> > ("Revert "RISC-V: mm: Document mmap changes"")
>
> Somehow I guess you didn't get the actual meaning behind this "Update xxx
> through commit...".
>
> Correct me if I'm wrong. If you write this line in your commit message.
> Then it means if we apply this patch of yours. The Chinese documentation
> of this file should be already _completely_ synchronized.
>
I agree. My fault again.
> However, the current translation of this file is missing this part:
>
> RISC-V Linux Kernel SV57
> ------------------------
>
> ... which is not translated/synchronized in your patch.
>
>
Didn't see that because I just used the tools/docs/checktransupdate.py script,
which cannot see the commits before ed843ae947f8 ("docs: move riscv under
arch"). That commit just moved the Chinese translation but was treated as an
update by the script. And I only looked at the commits reported by the script.
> Note that I'm not blaming on you for this. But I feel this is a point
> that a newcomer might find confusing, including me and Chen-Yu a couple
> of weeks ago, if did not read the script.
>
> Our current how-to.rst only asks to write this line in the commit
> message but does not explain the results or the actual work behind it.
>
> [...]
> Update the translation through commit b080e52110ea
> ("docs: update self-protection __ro_after_init status")
> # 请执行 git log --oneline <您翻译的英文文档路径>,并替换上述内容
>
> So when a newcomer comes and just does what this asks, without
> considering whether his/her/its translation is completely
> synchronized or not, our script would be kind of inaccurate. ?
>
> Maybe we can add a description or a hint like:
>
> If your current changes make the translation completely in line with the
> English version, then please add this line after your descriptions and
> before a blank line and your sign-off:
>
> Update the translation through commit e83c5163316f
> (Initial revision of "git", the information manager from hell)
>
> ..then follows a template commit message
Allowing partial updates to the translation?
>
>
> Any ideas?
>
> (Should I cc the original authors of the script?)
CC the authors of the checktransupdate.py script?
>
> Thanks.
Best,
Yukai Wu
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-08-30 1:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 4:15 [PATCH] docs/zh_CN: Update arch/riscv/vm-layout.rst translation Yukai Wu
2026-08-29 4:15 ` Yukai Wu
2026-08-29 15:32 ` Weijie Yuan
2026-08-29 15:32 ` Weijie Yuan
2026-08-30 1:33 ` Yukai Wu [this message]
2026-08-30 1:33 ` Yukai Wu
2026-08-30 4:55 ` Weijie Yuan
2026-08-30 4:55 ` Weijie Yuan
2026-08-29 16:57 ` Yao Zi
2026-08-29 16:57 ` Yao Zi
2026-08-30 14:32 ` Weijie Yuan
2026-08-30 14:32 ` Weijie Yuan
2026-08-30 18:53 ` Yao Zi
2026-08-30 18:53 ` Yao Zi
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=f-IgWNAyTmaoW34tfNxIvg@gmail.com \
--to=xiaoyewuz.ruster@gmail.com \
--cc=alex@ghiti.fr \
--cc=alexs@kernel.org \
--cc=aou@eecs.berkeley.edu \
--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=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--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 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.