All of lore.kernel.org
 help / color / mirror / Atom feed
From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	linux-man@vger.kernel.org
Subject: Re: NeoMutt + GMail signed patches (was Re: [PATCH 2/2] man-pages.7: Update non-breaking space advice.)
Date: Tue, 3 Aug 2021 11:34:13 +0200	[thread overview]
Message-ID: <20210803093413.ztdarccotobbbrht@tarta.nabijaczleweli.xyz> (raw)
In-Reply-To: <02923f47-b594-ce8f-68e4-ed9fc0f915af@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

On Tue, Aug 03, 2021 at 09:36:14AM +0200, Alejandro Colomar (man-pages) wrote:
> I found that Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> also sends signed patches,

FWIW, there isn't much of a trick to it, all I do is have
	[format]
		headers = "X-Mutt-PGP: OS\n"
in .gitconfig, then (cmdline verbatim for the patch you quoted):
	git format-patch --to='Alejandro Colomar <alx.manpages@gmail.com>' --cc='linux-man@vger.kernel.org' --stdout HEAD^ >> ~/mail/mailboxes/Drafts/messages

And just recall it in NeoMutt, the special header enables PGP OppEnc
(I used to just enable it manually for a while with <smime-menu>,
 which works, but got very old very fast).

Copying format-patch into drafts is an explicitly supported
configuration, and has been for decades (cf. git-format-patch(1),
DISCUSSION, 2nd paragraph ‒ active ia64 development dates it,
rest in peace).

> and digging through the source of an email,
> I found she also uses NeoMutt + GMail.
> But her patches always apply.

@nabijaczleweli.xyz is my local Postfix instance,
but this does also work on GMail (copying the mail from a temporary
mailbox into the drafts is a little iffy, but works);
you're seeing a lot of GMail headers because GMail received it.

> Cheers,
> Alex

Best,
наб

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-08-03  9:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31  3:45 [PATCH 2/2] man-pages.7: Update non-breaking space advice G. Branden Robinson
2021-07-31 11:42 ` Alejandro Colomar (man-pages)
2021-08-01 10:12   ` G. Branden Robinson
2021-08-01 10:49     ` Alejandro Colomar (man-pages)
2021-08-01 11:41       ` G. Branden Robinson
2021-08-01 12:30         ` Alejandro Colomar (man-pages)
2021-08-04  6:20           ` G. Branden Robinson
2021-08-03  7:36         ` NeoMutt + GMail signed patches (was Re: [PATCH 2/2] man-pages.7: Update non-breaking space advice.) Alejandro Colomar (man-pages)
2021-08-03  9:34           ` наб [this message]
2021-10-17 19:53     ` [PATCH 2/2] man-pages.7: Update non-breaking space advice Alejandro Colomar (man-pages)
2021-11-12 20:33       ` Ping^2: " Alejandro Colomar (man-pages)

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=20210803093413.ztdarccotobbbrht@tarta.nabijaczleweli.xyz \
    --to=nabijaczleweli@nabijaczleweli.xyz \
    --cc=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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.