All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
	Lorenzo Stoakes <ljs@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: Thu, 19 Nov 2026 11:07:13 +0100	[thread overview]
Message-ID: <b7474fd4-eb88-4472-9e8f-26ef6c646694@kernel.org> (raw)
In-Reply-To: <20261118212538.7e6f11f0553d548a03c9c456@linux-foundation.org>

On 11/19/26 06:25, Andrew Morton wrote:
> On Wed, 18 Nov 2026 11:21:47 +0100 "Vlastimil Babka (SUSE)" <vbabka@kernel.org> 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.
>> 
>> 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.
> 
> np, that should be working now.

Seems it is, thanks a lot!

> I switched it to patch.msgid.link for just the Link: to the original.

Yes "just to the original" is what I meant.

> Konstantin's
> https://lore.kernel.org/all/20240619-docs-patch-msgid-link-v2-2-72dd272bfe37@linuxfoundation.org/
> was helpful.
> 
> I hope patch.msgid.link is durable.  It's owned/operated by the LF so I
> guess it'll be there for a while!

Yeah. After all, the same is true for lore.kernel.org :)


      reply	other threads:[~2026-11-19 10:07 UTC|newest]

Thread overview: 4+ 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)
2026-11-19  5:25 ` Andrew Morton
2026-11-19 10:07   ` Vlastimil Babka (SUSE) [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=b7474fd4-eb88-4472-9e8f-26ef6c646694@kernel.org \
    --to=vbabka@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=rppt@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 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.