All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v1 0/5] Update the maintainer PGP guide
Date: Tue, 2 Aug 2022 11:07:21 +0200	[thread overview]
Message-ID: <YujpSWaISTWm8/8w@ada.ifak-system.com> (raw)
In-Reply-To: <20220727-docs-pgp-guide-v1-0-c48fb06cb9af@linuxfoundation.org>

Hallo Konstantin,

Am Thu, Jul 28, 2022 at 04:57:03PM -0400 schrieb Konstantin Ryabitsev:
> This series updates the guide to match terminology used in the upstream
> "protecting code integrity" guide [1] and brings the documentation in
> line with the latest developments in the GnuPG world:

I could not find [1]. Did you miss to add the footnote?

Greets
Alex

> - uses "Certify key" instead of "master key" terms to remove common
>   confusion that the "Certify key" is somehow able to restore lost
>   private subkeys
> - removes keyserver instructions because keyservers have largely gone
>   semi-extinct due to GDPR enforcement and just general neglect
> - adds a link to the kernel.org PGP keyring documentation
> - updates information about ECC curve support among the devices the
>   guide talks about (Yubikeys are able to use ED25519 curves with the
>   latest firmware updates)
> - adds a section on using PGP-signed patches with b4 and patatt
> 
> Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
> 
> ---
> Konstantin Ryabitsev (5):
>       maintainer-pgp-guide: use key terminology consistent with upstream
>       maintainer-pgp-guide: remove keyserver instructions
>       maintainer-pgp-guide: update ECC support information
>       maintainer-pgp-guide: add a section on PGP-signed patches
>       maintainer-pgp-guide: minor wording tweaks
> 
>  Documentation/process/maintainer-pgp-guide.rst | 287 ++++++++++++-------------
>  1 file changed, 142 insertions(+), 145 deletions(-)
> ---
> base-commit: e0dccc3b76fb35bb257b4118367a883073d7390e
> change-id: 20220727-docs-pgp-guide-1dfc91614c0f
> 
> Best regards,
> -- 
> Konstantin Ryabitsev <konstantin@linuxfoundation.org>

  parent reply	other threads:[~2022-08-02  9:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 20:57 [PATCH v1 0/5] Update the maintainer PGP guide Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 1/5] maintainer-pgp-guide: use key terminology consistent with upstream Konstantin Ryabitsev
2022-07-30 13:12   ` Wu XiangCheng
2022-08-02 17:07     ` Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 2/5] maintainer-pgp-guide: remove keyserver instructions Konstantin Ryabitsev
2022-07-29  1:47   ` Bagas Sanjaya
2022-08-02 17:21     ` Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 3/5] maintainer-pgp-guide: update ECC support information Konstantin Ryabitsev
2022-07-29  9:11   ` Bagas Sanjaya
2022-08-02 17:16     ` Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 4/5] maintainer-pgp-guide: add a section on PGP-signed patches Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 5/5] maintainer-pgp-guide: minor wording tweaks Konstantin Ryabitsev
2022-07-29 22:55   ` Randy Dunlap
2022-08-02 17:09     ` Konstantin Ryabitsev
2022-08-02  9:07 ` Alexander Dahl [this message]
2022-08-02 17:00   ` [PATCH v1 0/5] Update the maintainer PGP guide Konstantin Ryabitsev

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=YujpSWaISTWm8/8w@ada.ifak-system.com \
    --to=ada@thorsis.com \
    --cc=corbet@lwn.net \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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 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.