From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/5] stdio.3, signal-safety.7: srcfix
Date: Sat, 31 Aug 2024 21:56:08 -0500 [thread overview]
Message-ID: <20240901025608.xdapdc2xcsrsps4w@illithid> (raw)
In-Reply-To: <zza4c2qlbpbpn62lg5mbcutcjnbeaiwrosvpe2s3hlvbyjjdzc@3xb6pb2wa5v5>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
Hi Alex,
At 2024-09-01T00:27:38+0200, Alejandro Colomar wrote:
> On Sat, Aug 31, 2024 at 05:17:59PM GMT, G. Branden Robinson wrote:
> > At 2024-08-31T23:43:01+0200, Alejandro Colomar wrote:
> > > Any advances with git-send-email(1)?
> >
> > No--I'm still stuck on neomutt 20201127.
>
> I think that if you use --thread with git-format-patch(1),
[...]
> you'll be able to use neomutt(1) as you're doing now. The generated
> patches should contain pre-set In-Reply-To headers which refer to the
> first patch, which will have a pre-set Message-ID. Please check.
I will try this with my next set. With a handful of manual edits to
some oddball cases, I've gotten to this point:
$ wc -l ready.MR straggling.MR
17136 ready.MR
0 straggling.MR
17136 total
That means no more of \fBthese\fP(1).
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-09-01 2:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 18:20 [PATCH 3/5] namespaces.7: ffix G. Branden Robinson
2024-08-31 20:51 ` Alejandro Colomar
2024-08-31 21:23 ` [PATCH 1/5] stdio.3, signal-safety.7: srcfix G. Branden Robinson
2024-08-31 21:43 ` Alejandro Colomar
2024-08-31 22:17 ` G. Branden Robinson
2024-08-31 22:27 ` Alejandro Colomar
2024-09-01 2:56 ` G. Branden Robinson [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-31 18:20 [PATCH 2/5] syscalls.2, signal-safety.7, namespaces.7: srcfix G. Branden Robinson
2024-08-31 20:48 ` Alejandro Colomar
2024-08-31 18:20 [PATCH 1/5] stdio.3, signal-safety.7: srcfix G. Branden Robinson
2024-08-31 20:43 ` Alejandro Colomar
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=20240901025608.xdapdc2xcsrsps4w@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox