Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
* Using In-reply-to: <patch posting> in mm-commits mails?
@ 2026-11-18 10:21 Vlastimil Babka (SUSE)
  2026-11-18 12:09 ` Lorenzo Stoakes (ARM)
  0 siblings, 1 reply; 2+ messages in thread
From: Vlastimil Babka (SUSE) @ 2026-11-18 10:21 UTC (permalink / raw)
  To: Andrew Morton
  Cc: David Hildenbrand (Arm), Lorenzo Stoakes, Mike Rapoport,
	linux-mm@kvack.org, mm-commits

Hi Andrew,

during some chat with Lorenzo, it occured me that it could be useful if your
mm-commit mails (addition, merging to mm-stable, drop etc.) were replies to
the respective patch postings, which would put them next to the patches in
everyone's inboxes. I think Lorenzo started to doing that on his receive
side with postprocessing.

While I haven't checked your scripts, I naively imagine it shouldn't be hard
to add that In-reply-to: <msgid> header. You already have the msgid for the

Link: https://lore.kernel.org/<msgid>

part. Maybe it's tricky when there are more Link:'s than the patch posting
itself. But actually after Linus initially hated these automatic Link:
additions, he later settled on the Link: https://patch.msgid.link/ template
as acceptable to him. It's sort of documented in
Documentation/process/maintainer-tip.rst too. So changing to use that
template should allow to easily grab the right msgid to reply to even for
later actions on the patch, than the initial addition.

Thoughs?
Thanks,
Vlastimil


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Using In-reply-to: <patch posting> in mm-commits mails?
  2026-11-18 10:21 Using In-reply-to: <patch posting> in mm-commits mails? Vlastimil Babka (SUSE)
@ 2026-11-18 12:09 ` Lorenzo Stoakes (ARM)
  0 siblings, 0 replies; 2+ messages in thread
From: Lorenzo Stoakes (ARM) @ 2026-11-18 12:09 UTC (permalink / raw)
  To: Vlastimil Babka (SUSE)
  Cc: Andrew Morton, David Hildenbrand (Arm), Mike Rapoport,
	linux-mm@kvack.org, mm-commits

On Wed, Nov 18, 2026 at 11:21:47AM +0100, Vlastimil Babka (SUSE) wrote:
> Hi Andrew,
>
> during some chat with Lorenzo, it occured me that it could be useful if your
> mm-commit mails (addition, merging to mm-stable, drop etc.) were replies to
> the respective patch postings, which would put them next to the patches in
> everyone's inboxes. I think Lorenzo started to doing that on his receive
> side with postprocessing.

Ack to confirm I had claude schlopp me something to do that and it's already
extremely useful - let's me see at glance if a patch/series has been taken, etc.

Especially useful in neomutt set up to show emails hierarchically.

>
> While I haven't checked your scripts, I naively imagine it shouldn't be hard
> to add that In-reply-to: <msgid> header. You already have the msgid for the
>
> Link: https://lore.kernel.org/<msgid>
>
> part. Maybe it's tricky when there are more Link:'s than the patch posting
> itself. But actually after Linus initially hated these automatic Link:
> additions, he later settled on the Link: https://patch.msgid.link/ template
> as acceptable to him. It's sort of documented in
> Documentation/process/maintainer-tip.rst too. So changing to use that
> template should allow to easily grab the right msgid to reply to even for
> later actions on the patch, than the initial addition.

Should be straightforward I think?

>
> Thoughs?
> Thanks,
> Vlastimil

--
Cheers, Lorenzo


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-11-18 12:09 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-18 10:21 Using In-reply-to: <patch posting> in mm-commits mails? Vlastimil Babka (SUSE)
2026-11-18 12:09 ` Lorenzo Stoakes (ARM)

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox