From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>,
"G. Branden Robinson" <branden@debian.org>
Subject: [PATCH] CONTRIBUTING: neomutt(1) can now be used to sign patches
Date: Fri, 26 Jan 2024 14:27:50 +0100 [thread overview]
Message-ID: <20240126132722.6325-2-alx@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
Link: <https://github.com/neomutt/neomutt/issues/1471>
Link: <https://github.com/neomutt/neomutt/pull/4134>
Cc: "G. Branden Robinson" <branden@debian.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---
CONTRIBUTING | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/CONTRIBUTING b/CONTRIBUTING
index 803f9c542..de7ec595b 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -58,17 +58,14 @@ Description
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.
+ combination with neomutt(1). For that, do the following.
In <~/.gitconfig>, add the following section:
[sendemail]
- sendmailcmd = mutt -H - && true
+ sendmailcmd = neomutt -C -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>.
+ For now, you'll need to build neomutt(1) from source to do this.
Patches
If you know how to fix a problem in a manual page (if not, see
--
2.43.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-01-26 13:27 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=20240126132722.6325-2-alx@kernel.org \
--to=alx@kernel.org \
--cc=branden@debian.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 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.