Re: [PATCH 0/4] Update maintainer-pgp-guide.rst Chinese translation
From: Dongliang Mu
Date: Fri Aug 21 2026 - 07:20:01 EST
On 8/21/26 3:22 PM, Weijie Yuan wrote:
On Fri, Aug 21, 2026 at 02:54:59PM +0800, Dongliang Mu wrote:
On 8/21/26 1:13 AM, Weijie Yuan wrote:Hi!
The script says:Hi Weijie,
$ tools/docs/checktransupdate.py Documentation/translations/zh_CN/process/maintainer-pgp-guide.rst
[1787244823.341547] Documentation/translations/zh_CN/process/maintainer-pgp-guide.rst
[1787244823.630509] commit 54857c52452a ("docs: maintainer-pgp-guide.rst: add a reference for kernel.org sign")
[1787244823.680849] commit 6c5c07bc8589 ("docs: process: maintainer-pgp-guide: update kernel.org docs link")
[1787244823.730027] commit 273aa250f138 ("Documentation: Improve wording on requirements for a free Nitrokey")
[1787244823.779408] commit f44a29784f68 ("Documentation: update maintainer-pgp-guide for latest best practices")
[1787244823.779522] 4 commits needs resolving in total
So I updated this document in chronological order, created four patches
based on these four outdated commits to make it easier for you to
review. Hence, you can freely squash them when applying them.
Tested with make htmldocs, no warning or error made by these patches.
Please make sure you execute " make cleandocs & make htmldocs". Some
warnings may be ignored by further compilation.
Thanks for emphasizing this. While I do remember I used "make cleandocs
&& make htmldocs", and checked among those long lines of red warning
output to find anything caused by my commit, I indeed didn't notice this
warning appearing at the early stage of the compilation.
It seems that I need to have my eyes checked soon. ;-)
Apologize for my recklessness.
Even so, do we have any way to distinguish these long-standing warnings
from the new warnings that appear during compilation? In fact, every
time I was worried that I might not have noticed the newly appeared
warning. Unfortunately, this time it really happened. (For example,
setting a new color? for new warnings?) Do you have a better idea or
tips for this?
My suggestion is to keep the log in each file, and you can easily observe the diff. Otherwise, even I can ignore some warnings.
And many contributors are coming together to fix those warnings. If they are done, all new warnings are easily captured. Let us do more contribution to help this.
Dongliang Mu
Btw I've been trying to know more about Sphinx and kernel-docs, hope my
mistake won't happen again.
That change can fix problem. The underlying problem is RST syntax. Maybe you can have a look at this or query it in the LLM.
Dongliang Mu
Thanks.
> WARNING: duplicate label kernel_org_trust_repository
>
> The same label is already defined in the English document. Please use a translation-specific label, for example:
>
> .. _zh_kernel_org_trust_repository:
> checkpatch.pl reports:And this one has been updated from Jon's PR last night, so I ignored
>
> WARNING: Assisted-by expects 'AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]' format
>
> Please replace Assisted-by: LLM with the actual agent, model version, and tools used.
this output, left just a simple LLM.