From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>,
Matthew House <mattlloydhouse@gmail.com>
Subject: [PATCH v2] CONTRIBUTING: Please sign your emails with PGP
Date: Wed, 22 Nov 2023 14:47:58 +0100 [thread overview]
Message-ID: <20231122134716.73658-2-alx@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]
Cc: Matthew House <mattlloydhouse@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---
CONTRIBUTING | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/CONTRIBUTING b/CONTRIBUTING
index 475244c13..7b85e7375 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -56,6 +56,29 @@ Description
help
+ Sign your emails with PGP
+ It is strongly encouraged that you sign all of your emails sent
+ to the mailing list, (especially) including the ones containing
+ patches, with your PGP key. This helps establish trust between
+ you and other contributors of this project, and prevent others
+ impersonating you. If you don't have a key, it's not mandatory
+ to sign your email, but you're encouraged to create and start
+ using a PGP key.
+
+ There are many ways you can sign your patches, and it depends on
+ your preferred tools. You can use git-send-email(1) in
+ combination with mutt(1). For that, do the following.
+
+ In <~/.gitconfig>, add the following section:
+
+ [sendemail]
+ sendmailcmd = mutt -H - && true
+
+ And then, patch mutt(1) to enable encryption in batch and mailx
+ modes, which is disabled in upstream mutt(1). You can find a
+ patch here:
+ <https://gitlab.com/muttmua/mutt/-/merge_requests/173>.
+
Patches
If you know how to fix a problem in a manual page (if not, see
"Reporting bugs" below), then send a patch in an email.
--
2.42.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-11-22 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 13:47 Alejandro Colomar [this message]
2023-11-22 16:25 ` [PATCH v2] CONTRIBUTING: Please sign your emails with PGP G. Branden Robinson
2023-11-22 17:26 ` Alejandro Colomar
2023-11-22 18:50 ` G. Branden Robinson
2023-11-22 20:08 ` Alejandro Colomar
2023-11-22 20:19 ` Errata in K&R C v2, page 97 (was: [PATCH v2] CONTRIBUTING: Please sign your emails with PGP) Alejandro Colomar
[not found] ` <41b65637907f43ecafadd58565a7b483@DM6PR04MB4443.namprd04.prod.outlook.com>
2023-11-26 14:57 ` Brian Kernighan
2023-11-26 15:47 ` Alejandro Colomar
2023-11-26 15:49 ` Alejandro Colomar
2023-11-26 15:54 ` Brian Kernighan
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=20231122134716.73658-2-alx@kernel.org \
--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 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.