mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-mm@kvack.org,  mm-commits@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] MM updates for 7.1-rc1
Date: Thu, 23 Apr 2026 10:44:59 -0400	[thread overview]
Message-ID: <20260423-tasteful-stingray-from-sirius-7b94bb@lemur> (raw)
In-Reply-To: <20260423051246.5de8968ca017eeb8f053fbff@linux-foundation.org>

On Thu, Apr 23, 2026 at 05:12:46AM -0700, Andrew Morton wrote:
> But what is the preferred, official URL?   Any preferences?

Its in
https://docs.kernel.org/process/submitting-patches.html#describe-your-changes:

    When linking to mailing list archives, preferably use the lore.kernel.org
    message archiver service. To create the link URL, use the contents of the
    Message-ID header of the message without the surrounding angle brackets. For
    example:

    Link: https://lore.kernel.org/30th.anniversary.repost@klaava.Helsinki.FI
    Please check the link to make sure that it is actually working and points to the relevant message.

However if the link is purely to indicate commit provenance ("this commit came
from the patch posted here"), use the dedicated patch.msgid.link domain, e.g.:

    Link: https://patch.msgid.link/{MSGID}

-K

  reply	other threads:[~2026-04-23 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14  4:49 Andrew Morton
2026-04-15 20:20 ` Linus Torvalds
2026-04-16  8:18   ` Andrew Morton
2026-04-22 20:38     ` Konstantin Ryabitsev
2026-04-23 12:12       ` Andrew Morton
2026-04-23 14:44         ` Konstantin Ryabitsev [this message]
2026-04-15 20:35 ` pr-tracker-bot

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=20260423-tasteful-stingray-from-sirius-7b94bb@lemur \
    --to=konstantin@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®