From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"David Hildenbrand (Arm)" <david@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
mm-commits@vger.kernel.org
Subject: Re: Using In-reply-to: <patch posting> in mm-commits mails?
Date: Wed, 18 Nov 2026 12:09:44 +0000 [thread overview]
Message-ID: <av2UtIIP202zN2jJ@gremlin> (raw)
In-Reply-To: <9ba54069-3dc4-422f-8cf6-f81cb806e999@kernel.org>
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
prev parent reply other threads:[~2026-11-18 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=av2UtIIP202zN2jJ@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=vbabka@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