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: Wed, 22 Apr 2026 16:38:52 -0400 [thread overview]
Message-ID: <20260422-aquatic-chital-of-wealth-8b7fa3@meerkat> (raw)
In-Reply-To: <20260416011820.18f5a11bbed7fff54be761e2@linux-foundation.org>
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.
-K
next prev parent reply other threads:[~2026-04-22 20:38 UTC|newest]
Thread overview: 5+ 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 [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=20260422-aquatic-chital-of-wealth-8b7fa3@meerkat \
--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