Linux Documentation
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
	 Dongliang Mu <dzm91@hust.edu.cn>,
	Jonathan Corbet <corbet@lwn.net>,
	 Shuah Khan <skhan@linuxfoundation.org>,
	 Randy Dunlap <rdunlap@infradead.org>,
	 Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/5] docs/zh_CN: update maintainer-pgp-guide kernel.org link
Date: Sun, 23 Aug 2026 15:14:59 +0800	[thread overview]
Message-ID: <20260823-maintainer-pgp-guide-v2-3-bea33b2ece54@wyuan.org> (raw)
In-Reply-To: <20260823-maintainer-pgp-guide-v2-0-bea33b2ece54@wyuan.org>

Update the kernel.org documentation link for adding a kernel.org UID.
The SPDX identifier added upstream already exists in the Chinese
translation.

Update the translation through commit 6c5c07bc8589
("docs: process: maintainer-pgp-guide: update kernel.org docs link")

Signed-off-by: Weijie Yuan <wy@wyuan.org>
---
The SPDX identifier of this translation was added at its birth, while
the SPDX identifier of its original English version was added this year
2026. Although it has been added, I'm quite curious about whether it is
"legal" to add the identifier on top of the Chinese translation while
the English original does not have one back in 2023.

I know Jon has been a little bit careful about it, so I'd better leave
my thoughts here for future reference.

Thanks.
---
 Documentation/translations/zh_CN/process/maintainer-pgp-guide.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/translations/zh_CN/process/maintainer-pgp-guide.rst b/Documentation/translations/zh_CN/process/maintainer-pgp-guide.rst
index b329755cc960..6e29c9a74f4c 100644
--- a/Documentation/translations/zh_CN/process/maintainer-pgp-guide.rst
+++ b/Documentation/translations/zh_CN/process/maintainer-pgp-guide.rst
@@ -753,7 +753,7 @@ Greg Kroah-Hartman 的密钥(如果你还没有它们)::
 如果你有 kernel.org 帐户,那么你应该 `添加 kernel.org UID 到你的密钥中`_
 添加到你的密钥中,以使 WKD 对其他内核开发人员更有用。
 
-.. _`添加 kernel.org UID 到你的密钥中`: https://korg.wiki.kernel.org/userdoc/mail#adding_a_kernelorg_uid_to_your_pgp_key
+.. _`添加 kernel.org UID 到你的密钥中`: https://korg.docs.kernel.org/mail.html#adding-a-kernel-org-uid-to-your-pgp-key
 
 信任网 (WOT) 与首次使用信任 (TOFU)
 -----------------------------------

-- 
2.55.0.822.g20453c30eb


  parent reply	other threads:[~2026-08-23  7:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23  7:14 [PATCH v2 0/5] Update maintainer-pgp-guide.rst Chinese translation Weijie Yuan
2026-08-23  7:14 ` [PATCH v2 1/5] docs/zh_CN: update maintainer-pgp-guide translation Weijie Yuan
2026-08-23  7:14 ` [PATCH v2 2/5] docs/zh_CN: clarify free Nitrokey requirements Weijie Yuan
2026-08-23  7:14 ` Weijie Yuan [this message]
2026-08-23  7:15 ` [PATCH v2 4/5] docs/zh_CN: add kernel.org trust repository reference Weijie Yuan
2026-08-23  7:15 ` [PATCH v2 5/5] docs/zh_CN: remove empty proofreader field from maintainer PGP guide Weijie Yuan

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=20260823-maintainer-pgp-guide-v2-3-bea33b2ece54@wyuan.org \
    --to=wy@wyuan.org \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=si.yanteng@linux.dev \
    --cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox