From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: maintainer-pgp-guide: update for latest gnupg defaults
Date: Thu, 22 Dec 2022 10:43:28 -0500 [thread overview]
Message-ID: <20221222154328.lort3wvixcyykeyx@nitro.local> (raw)
In-Reply-To: <Y6RVTQxhcxDDrvO3@debian.me>
On Thu, Dec 22, 2022 at 08:02:05PM +0700, Bagas Sanjaya wrote:
> Shouldn't "Protecting Code Integrity" doc also be updated with recent
> situation?
Yes, I'm working on updating that document as well. By the time this change
makes it into mainline, both documents will be a close match.
> LGTM, thanks.
>
> Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Thanks!
-K
next prev parent reply other threads:[~2022-12-22 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 19:44 [PATCH] docs: maintainer-pgp-guide: update for latest gnupg defaults Konstantin Ryabitsev
2022-12-22 13:02 ` Bagas Sanjaya
2022-12-22 15:43 ` Konstantin Ryabitsev [this message]
2023-01-02 23:38 ` 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=20221222154328.lort3wvixcyykeyx@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox