From: Alejandro Colomar <alx@kernel.org>
Date: Fri, 26 Jan 2024 13:24:50 +0000 (+0100)
Subject: CONTRIBUTING: neomutt(1) can now be used to sign patches
X-Git-Tag: man-pages-6.06~12
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bd7badfdf16ef975af4af3dfd3829319bcd567dd;p=thirdparty%2Fman-pages.git

CONTRIBUTING: neomutt(1) can now be used to sign patches

Link: <https://github.com/neomutt/neomutt/issues/1471>
Link: <https://github.com/neomutt/neomutt/pull/4134>
Link: <https://neomutt.org/feature/cli-crypto>
Cc: "G. Branden Robinson" <branden@debian.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 803f9c5426..c113803fb2 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -57,18 +57,12 @@ Description
         <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 git-send-email(1) in
-        combination with mutt(1).  For that, do the following.
-
-        In <~/.gitconfig>, add the following section:
+        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 = 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>.
+                sendmailcmd = neomutt -C -H - && true
 
    Patches
        If you know how to fix a problem in a manual page (if not, see