Hi, Pengyu
在 2024/10/11 23:49, Pengyu Zhang 写道:
Hi, Yanteng
在 2024/10/11 09:47, Yanteng Si 写道:
Hi Pengyu,
在 2024/10/8 23:38, Pengyu Zhang 写道:
This patch provides a Simplified Chinese translation of the
"page_tables.rst" document, aimed at improving accessibility
for Chinese-speaking developers and users.
The translation prioritizes technical accuracy and readability,
ensuring that the content remains clear and informative for
its intended audience.
Let's add a commit tag so that the scripts/checktransupdate.py can
recognize it. just like:
Subject:[PATCH v3] docs/zh_CN: add the translation of kbuild/gcc-plugins.rst <https://lore.kernel.org/linux-doc/20240907070244.206808-1-dzm91@xxxxxxxxxxx/#r>
Date: Sat, 7 Sep 2024 15:02:08 +0800
Finish the translation of kbuild/gcc-plugins.rst and move gcc-plugins
from TODO to the main body.
Update to commit 3832d1fd84b6 ("docs/core-api: expand Fedora instructions
for GCC plugins")
Thanks，
Yanteng
Sorry, my email client sent an HTML email and I have fixed it. Now resend
to the mailing list.
Thanks,
Yanteng
We discovered a pfn calculation error during the translation of the
page_tables.rst. I have submitted another patch to fix it, and it had been
reviewed by three maintainers, but it has not yet been merged into the mainline.
https://lore.kernel.org/all/20241009144135.12453-1-zpenya1314@xxxxxxxxx/
So I have a question: should the commit tag be based on the fix patch
I submitted, or the tag of the original page_tables.rst?
Hmm, I think you can ignore this tag in the next version and specify the
reason in the commit message, which will also be helpful for future
updates. Of course, there may be a better way, which is to modify this
tag when Jon applies the patch, but I'm not sure if this will work.
Of course, there is another great method, which is to still ignore this
tag and split your translation patch into two patch：
Patch 1 ：only translates English documents （with tag);
Patch 2 ：fixes the pfn calculation error in the Chinese document.
put them into a patch sets.
git am <Patch 1>
git am
<https://lore.kernel.org/all/20241009144135.12453-1-zpenya1314@xxxxxxxxx/>
## Remember to pick up the review tag
git am <Patch 2>
git format-patch -3 -v 5 --cover-letter
vim 0000-cover-letterxxx.patch
git send-email v5*
Thanks,
Yanteng
Thanks,
Pengyu
