From: Alejandro Colomar <alx@kernel.org>
To: Matthew House <mattlloydhouse@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: Signing all patches and email to this list
Date: Thu, 16 Nov 2023 00:39:07 +0100 [thread overview]
Message-ID: <ZVVWmz1Lfh3wplBE@devuan> (raw)
In-Reply-To: <20231115232848.693843-1-mattlloydhouse@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Hi Matthew,
On Wed, Nov 15, 2023 at 06:28:42PM -0500, Matthew House wrote:
> > + Sign your emails with PGP
> > + Please sign all of your emails sent to the mailing list,
> > + including your emails containing patches, with your PGP
> > + key. This helps establish trust between you and other
> > + contributors of this project, and prevent others
> > + impersonating you.
>
> If this is meant to be a suggestion rather than an obligation, then I'd
> prefer if it had an explicit statement to the effect that it is (strongly?)
> encouraged but not mandatory. If I were reading CONTRIBUTING for the first
> time, I'd be inclined to read the bare imperative "Please sign all of your
> emails" as a hard requirement, and be scared off on account of not even
> having a PGP key.
Yep, I was worried I would scare off those who don't even have one.
Thanks for the suggestion; will update accordingly.
Cheers,
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-15 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231115212015.6446-1-alx@kernel.org>
2023-11-15 23:28 ` Signing all patches and email to this list Matthew House
2023-11-15 23:39 ` Alejandro Colomar [this message]
2023-11-13 23:46 Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2023-11-04 11:27 strncpy clarify result may not be null terminated Jonny Grant
2023-11-12 11:26 ` [PATCH v2 1/3] string_copying.7: BUGS: *cat(3) functions aren't always bad Alejandro Colomar
2023-11-17 21:43 ` Jonny Grant
2023-11-18 0:25 ` Signing all patches and email to this list Matthew House
2023-11-18 23:24 ` Jonny Grant
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=ZVVWmz1Lfh3wplBE@devuan \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mattlloydhouse@gmail.com \
/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