From: Paolo Bonzini <pbonzini@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [GIT PULL] Second batch of KVM changes for Linux 6.13
Date: Sun, 1 Dec 2024 00:21:38 +0100 [thread overview]
Message-ID: <c43676a2-8db6-4ff1-b519-3fd3aa290e4b@redhat.com> (raw)
In-Reply-To: <CAHk-=wjP5pBmMLpGtb=G7wUed5+CXSSAa0vfc-ZKgLHPvDpUqg@mail.gmail.com>
On 12/1/24 00:11, Linus Torvalds wrote:
> On Fri, 29 Nov 2024 at 15:18, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> This was acked on the mailing list by the RISC-V maintainer, see
>> https://patchew.org/linux/20240726084931.28924-1-yongxuan.wang@sifive.com/
>
> Please don't use random links. Maybe patchew will stay around. Maybe
> it won't. This is the first I ever see of it.
I'm not surprised. :) I'm going to launch into a full comparison of
lore/patchwork/patchew---but the reason why I used patchew this time, is
that I wanted to make sure that the one that was acked and included was
the most recent submission for this series (see for example the top of
https://patchew.org/linux/20240712083850.4242-1-yongxuan.wang@sifive.com/,
which was a previous version and has a link to the newest).
> It seems to be maintained by Red Hat, and yes, at least it contains
> the email message ID as part of the URL.
>
> But when I tried to go to patchew.org and then click on lkml.org, I
> get " https://patchew.org/lkml.org/" and a big "Not found" page.
>
> And when I clicked on "Linux", I get a working page, I can't even see
> the raw messages without downloading some "patch mbox".
>
> So "maintained" is perhaps too strong a word.
Fair enough. :) I can certainly stick to lore links if you prefer that.
Paolo
next prev parent reply other threads:[~2024-11-30 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 23:18 Paolo Bonzini
2024-11-30 23:11 ` Linus Torvalds
2024-11-30 23:21 ` Paolo Bonzini [this message]
2024-11-30 23:42 ` Linus Torvalds
2024-11-30 23:15 ` 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=c43676a2-8db6-4ff1-b519-3fd3aa290e4b@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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®