From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Subject: Signing all patches and email to this list
Date: Tue, 14 Nov 2023 00:46:03 +0100 [thread overview]
Message-ID: <ZVK1POLjAID434nL@debian> (raw)
[-- Attachment #1: Type: text/plain, Size: 2214 bytes --]
Hi,
I'd like to ask contributors to sign their emails to this list with a
PGP key; especially for mails that include patches, but ideally all of
them. Of course, it's a suggestion, and there wouldn't be any
enforcement other than asking. What do you think of that?
I've prepared some text for ./CONTRIBUTING; please review. It also
depends on mutt(1) maintainers, if they want to patch mutt(1) to allow
crypto operations in batch and mailx modes.
Thanks,
Alex
---
commit f7ba049d975a4b323c8086b2fc859687e4fc1d4e (HEAD -> sign)
Author: Alejandro Colomar <alx@kernel.org>
Date: Fri Nov 10 01:10:00 2023 +0100
CONTRIBUTING: Please sign your emails with PGP
Signed-off-by: Alejandro Colomar <alx@kernel.org>
diff --git a/CONTRIBUTING b/CONTRIBUTING
index 475244c13..204e04fb3 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -56,6 +56,29 @@ Description
help
+ 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.
+
+ 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, patched mutt(1) to enable encryption in batch and
+ mailx modes, which is disabled in upstream mutt(1).
+ Hopefully, mutt(1) will merge the patch, so it'd be easier
+ to do this. You can find the 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.
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-11-13 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 23:46 Alejandro Colomar [this message]
[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
-- 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=ZVK1POLjAID434nL@debian \
--to=alx@kernel.org \
--cc=linux-man@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).