public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.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 05:12:46 -0700	[thread overview]
Message-ID: <20260423051246.5de8968ca017eeb8f053fbff@linux-foundation.org> (raw)
In-Reply-To: <20260422-aquatic-chital-of-wealth-8b7fa3@meerkat>

On Wed, 22 Apr 2026 16:38:52 -0400 Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:

> On Thu, Apr 16, 2026 at 01:18:20AM -0700, Andrew Morton wrote:
> > > The proper format would seem to be
> > > 
> > >     https://lore.kernel.org/all/aaGiDINfnUexT9Px@sirena.org.uk/
> > > 
> > > (or "lkml" instead of "all" if you want to be more specific).
> > > 
> > > Maybe something changed recently, or maybe your scripting for this is
> > > just broken?
> > > 
> > 
> > Something changed recently.  Maybe Konstantin knows.
> 
> It's a temporary blocking measure against aggressive crawlers. We'll restore
> this functionality shortly.
> 
> > I've always used https://lkml.kernel.org/r/MSGID.  So at present there
> > are many thousands of broken links in the kernel tree.
> 
> Well, the upside of this scheme is that they are only broken for clicking, but
> they can all still be found using the MSGID. However, as I said, this will
> soon be restored once we migrate the system serving lkml.kernel.org hits.

OK, thanks.

But what is the preferred, official URL?   Any preferences?


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14  4:49 [GIT PULL] MM updates for 7.1-rc1 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 [this message]
2026-04-23 14:44         ` Konstantin Ryabitsev
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=20260423051246.5de8968ca017eeb8f053fbff@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=konstantin@linuxfoundation.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