From: Amitabh <amitabh@amidevlab.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] docs: process: maintainer-pgp-guide: update kernel.org docs link
Date: Thu, 5 Feb 2026 19:44:05 +0530 [thread overview]
Message-ID: <208E3D71-B2A9-4428-958F-915E6FC95D4F@amidevlab.com> (raw)
In-Reply-To: <CAMuHMdVdBoXKg-7wDshMRGi05LiCOi62ETYzyV5HFbQXLinK6A@mail.gmail.com>
Hi Geert,
Hope this clarifies.
> On 5 Feb 2026, at 6:53 PM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> Hi Amitabh,
>
> Thanks for your patch!
>
> On Thu, 5 Feb 2026 at 13:09, Amitabh Srivastava <amitabh@amidevlab.com> wrote:
>> Update http link to the documentation about how to add a kernel.org UID to
>> the maintainer's key. Add missing SPDX-License-Identifier to fix a
>> checkpatch warning.
>
> > The first sentence states the obvious, but does not explain the
> > rationale behind this change. Why should it be changed? Both the
> > old and the new URL work.
> The old URL no longer points to the correct page having mentioned information.
> [Old URL]: Simply redirects to 'https://korg.docs.kernel.org/', which doesn't have any information on how to add the kernel.org UID to your PGP key.
> [New URL]: Precisely opens the respective page at the anchor for the respective section 'Adding a kernel.org UID to your PGP key'.
>> Signed-off-by: Amitabh Srivastava <amitabh@amidevlab.com>
>
>> --- a/Documentation/process/maintainer-pgp-guide.rst
>> +++ b/Documentation/process/maintainer-pgp-guide.rst
>> @@ -1,3 +1,5 @@
>> +.. SPDX-License-Identifier: GPL-2.0
>> +
>> .. _pgpguide:
>>
>> ===========================
>> @@ -864,7 +866,7 @@ don't already have them)::
>> If you have a kernel.org account, then you should `add the kernel.org
>> UID to your key`_ to make WKD more useful to other kernel developers.
>>
>> -.. _`add the kernel.org UID to your key`: https://korg.wiki.kernel.org/userdoc/mail#adding_a_kernelorg_uid_to_your_pgp_key
>> +.. _`add the kernel.org UID to your key`: https://korg.docs.kernel.org/mail.html#adding-a-kernel-org-uid-to-your-pgp-key
>>
>> Web of Trust (WOT) vs. Trust on First Use (TOFU)
>> ------------------------------------------------
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus TorvaldsThanks
> Regards
> Amitabh
next prev parent reply other threads:[~2026-02-05 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 11:55 Amitabh Srivastava
2026-02-05 13:23 ` Geert Uytterhoeven
2026-02-05 14:14 ` Amitabh [this message]
2026-02-05 14:49 ` Jonathan Corbet
2026-02-05 15:15 ` Amitabh
2026-02-05 15:30 ` Jonathan Corbet
[not found] ` <3AB51D59-A054-4847-91CD-DFF3A2EB5F04@amidevlab.com>
2026-02-06 14:20 ` Konstantin Ryabitsev
2026-02-06 14:38 ` Konstantin Ryabitsev
2026-02-06 16:04 ` Jonathan Corbet
2026-02-06 20:43 ` Amitabh
2026-02-09 19:51 ` Jonathan Corbet
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=208E3D71-B2A9-4428-958F-915E6FC95D4F@amidevlab.com \
--to=amitabh@amidevlab.com \
--cc=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@vger.kernel.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