From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>, Simon Barth <simon.barth@gmx.de>
Subject: [PATCH] CONTRIBUTING.d/: Clarify how to send patches with git-send-email(1)
Date: Fri, 26 Apr 2024 16:26:26 +0200 [thread overview]
Message-ID: <20240426142623.24922-1-alx@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2807 bytes --]
Cc: Simon Barth <simon.barth@gmx.de>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---
CONTRIBUTING.d/mail | 8 --------
CONTRIBUTING.d/patches | 27 ++++++++++++++++++++++++++-
2 files changed, 26 insertions(+), 9 deletions(-)
diff --git a/CONTRIBUTING.d/mail b/CONTRIBUTING.d/mail
index 48e5b9a93..fc75b9eee 100644
--- a/CONTRIBUTING.d/mail
+++ b/CONTRIBUTING.d/mail
@@ -51,14 +51,6 @@ Description
using a PGP key. See also:
<https://www.gnupg.org/faq/gnupg-faq.html#use_pgpmime>
- There are many ways you can sign your patches, and it depends on
- your preferred tools. You can use neomutt(1) (>= 20240201) as a
- driver for git-send-email(1). In <~/.gitconfig>, add the
- following section:
-
- [sendemail]
- sendmailcmd = neomutt -C -H - && true
-
See also
CONTRIBUTING
CONTRIBUTING.d/*
diff --git a/CONTRIBUTING.d/patches b/CONTRIBUTING.d/patches
index 96550ce0e..b4de1cf9f 100644
--- a/CONTRIBUTING.d/patches
+++ b/CONTRIBUTING.d/patches
@@ -6,7 +6,8 @@ Description
<CONTRIBUTING.d/bugs>), then send a patch in an email.
- Follow the instructions for sending mail to the mailing list
- from <CONTRIBUTING.d/mail>.
+ from <CONTRIBUTING.d/mail>. See also "Send the patches"
+ below.
- The subject of the email should contain "[patch]" in the
subject line.
@@ -87,8 +88,32 @@ Description
- Make patches against the latest version of the manual page.
Use git(1) for getting the latest version.
+
+ Send the patches
+ We recommend using git-send-email(1) to send the patches to the
+ mailing list. For instructions on how to configure and use it,
+ see <https://git-send-email.io/>. It can also be configured to
+ use mutt(1), which only requires the following section in
+ <~/.gitconfig> (assuming mutt(1) is already configured for
+ sending mail):
+
+ [sendemail]
+ sendmailcmd = mutt -H - && true
+
+ Sign the patches with PGP
+ See <CONTRIBUTING.d/mail> for more details on signing your mail
+ to the list. git-send-email(1) can be configured to use a recent
+ version of neomutt(1) (>= 20240201) with the -C flag, to sign
+ patches with PGP (assuming neomutt(1) is already configured for
+ sending signed mail):
+
+ [sendemail]
+ sendmailcmd = neomutt -C -H - && true
+
See also
CONTRIBUTING
CONTRIBUTING.d/*
<https://www.kernel.org/doc/Documentation/process/submitting-patches.rst>
+ <https://git-send-email.io/>
+ <https://neomutt.org/feature/cli-crypto>
--
2.43.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-04-26 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240426142623.24922-1-alx@kernel.org \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=simon.barth@gmx.de \
/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).