Link: <https://github.com/neomutt/neomutt/issues/1471> Link: <https://github.com/neomutt/neomutt/pull/4134> Cc: "G. Branden Robinson" <branden@xxxxxxxxxx> Signed-off-by: Alejandro Colomar <alx@xxxxxxxxxx> --- 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:
signature.asc
Description: PGP signature
