From: Paolo Bonzini <pbonzini@redhat.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Julia Lawall <julia.lawall@inria.fr>
Cc: Pratyush Yadav <pratyush@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Pavel Machek <pavel@ucw.cz>,
users@linux.kernel.org, ksummit@lists.linux.dev
Subject: Re: RFC: switching "THE REST" in MAINTAINERS away from linux-kernel@vger.kernel.org
Date: Tue, 7 Nov 2023 17:43:20 +0100 [thread overview]
Message-ID: <cefe4c99-2af9-4e22-a448-801a7080fc48@redhat.com> (raw)
In-Reply-To: <20231107-skilled-calculating-frigatebird-8db1bb@nitro>
On 11/7/23 17:35, Konstantin Ryabitsev wrote:
> I assume you're asking if following links to lkml.kernel.org/r/<msgid>
> is still going to find the thread? If that's the case, then yes, it's
> really just a redirect to lore.kernel.org/all/, which aggregates
> everything across all lists indexed by lore.kernel.org. You can
> similarly search in /all/ for the subjects matching commits if you don't
> have a Link:. In other words, this functionality is not affected by
> which list the patches were sent to.
What about _pulling_ all patches from public-inbox? Right now the git
repos under https://lore.kernel.org/lkml/ do not catch everything, but
it's close enough. There would be no https://lore.kernel.org/all/1.git/
and, even if there were, there is no easy way to filter out non-Linux
projects.
Paolo
next prev parent reply other threads:[~2023-11-07 16:43 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 15:33 RFC: switching "THE REST" in MAINTAINERS away from linux-kernel@vger.kernel.org Konstantin Ryabitsev
2023-11-06 15:43 ` Joe Perches
2023-11-06 15:52 ` Borislav Petkov
2023-11-06 16:05 ` [workflows]RFC: " Steven Rostedt
2023-11-06 16:29 ` Miquel Raynal
2023-11-06 17:45 ` Konstantin Ryabitsev
2023-11-08 16:19 ` Joe Perches
2023-11-08 16:44 ` Mark Brown
2023-11-08 18:16 ` Joe Perches
2023-11-08 19:04 ` Steven Rostedt
2023-11-08 19:14 ` Joe Perches
2023-11-08 19:34 ` Steven Rostedt
2023-11-08 20:07 ` [workflows]Re: " Steven Rostedt
2023-11-08 20:14 ` Joe Perches
2023-11-08 20:36 ` Joe Perches
2023-11-08 20:49 ` Joe Perches
2023-11-08 20:56 ` Steven Rostedt
2023-11-08 21:04 ` Konstantin Ryabitsev
2023-11-08 21:11 ` Steven Rostedt
2023-11-08 20:41 ` Joe Perches
2023-11-09 11:21 ` Mark Brown
2023-11-09 11:29 ` Laurent Pinchart
2023-11-09 8:32 ` Dan Carpenter
2023-11-09 9:27 ` Laurent Pinchart
2023-11-09 17:14 ` Alex Elder
2023-11-09 17:25 ` Konstantin Ryabitsev
2023-11-09 19:11 ` Joe Perches
2023-11-09 19:38 ` Konstantin Ryabitsev
2023-11-09 23:16 ` Jason Gunthorpe
2023-11-10 0:56 ` Linus Torvalds
2023-11-10 17:04 ` Jakub Kicinski
2023-11-10 17:24 ` Konstantin Ryabitsev
2023-11-10 17:55 ` Jakub Kicinski
2023-11-10 17:24 ` Rob Herring
2023-11-10 18:04 ` Jakub Kicinski
2023-11-09 15:51 ` Steven Rostedt
2023-11-09 16:08 ` Laurent Pinchart
2023-11-09 16:16 ` Steven Rostedt
2023-11-06 16:11 ` RFC: " Eric W. Biederman
2023-11-06 17:05 ` Christoph Hellwig
2023-11-06 17:41 ` Konstantin Ryabitsev
2023-11-09 3:55 ` Ian Kelling
2023-11-11 16:57 ` Theodore Ts'o
2023-11-07 4:04 ` Willy Tarreau
2023-11-06 17:21 ` Eric Wong
2023-11-06 17:56 ` Eric W. Biederman
2023-11-09 14:24 ` Naveen N Rao
2023-11-06 17:23 ` Richard Weinberger
2023-11-06 20:52 ` Randy Dunlap
2023-11-06 21:37 ` Jakub Kicinski
2023-11-06 22:52 ` Pavel Machek
2023-11-07 9:18 ` Paolo Bonzini
2023-11-07 10:15 ` Laurent Pinchart
2023-11-07 10:42 ` Greg KH
2023-11-07 12:14 ` Pratyush Yadav
2023-11-07 12:47 ` Julia Lawall
2023-11-07 13:18 ` Dan Carpenter
2023-11-07 13:23 ` Pratyush Yadav
2023-11-07 16:35 ` Konstantin Ryabitsev
2023-11-07 16:43 ` Paolo Bonzini [this message]
2023-11-07 16:51 ` Konstantin Ryabitsev
2023-11-10 10:01 ` Paolo Bonzini
2023-11-07 10:47 ` Mark Brown
2023-11-07 13:24 ` Dan Carpenter
2023-11-08 20:04 ` Bird, Tim
2023-11-08 21:03 ` Luck, Tony
2023-11-08 21:04 ` James Bottomley
2023-11-08 21:18 ` Johannes Berg
2023-11-08 21:30 ` Rob Herring
2023-11-21 14:53 ` Joe Perches
2023-11-21 18:08 ` Greg KH
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=cefe4c99-2af9-4e22-a448-801a7080fc48@redhat.com \
--to=pbonzini@redhat.com \
--cc=julia.lawall@inria.fr \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=pavel@ucw.cz \
--cc=pratyush@kernel.org \
--cc=users@linux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).