mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH v2] KVM: MAINTAINERS: note that linux-kvm.org isn't current
Date: Mon, 5 Jun 2023 18:48:44 +0200	[thread overview]
Message-ID: <b75c9696-9abb-7a3f-0fb2-56af8ef21bb6@redhat.com> (raw)
In-Reply-To: <ZHqSYbYscprsU2qT@google.com>

On 6/3/23 03:07, Sean Christopherson wrote:
> It's definitely stale, though unless Red Hat (presumed hoster) plans on decomissioning
> the site, I'd prefer to keep the reference and instead improve the site.  We (Google)
> are planning on committing resources to update KVM documentation that doesn't belong
> in the kernel itself, and updatingwww.linux-kvm.org  instead of creating something new
> seems like a no-brainer.  I can't promise an updates will happen super quickly, but I
> will do what I can to make 'em happen sooner than later.

We don't plan to decommission the website (especially not the old KVM 
Forum content), though we might move it over to the same 
(container-based) setup as wiki.qemu.org.

What content do you have in mind that doesn't fit in the kernel 
Documentation/ tree?

Paolo


  parent reply	other threads:[~2023-06-05 16:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 15:32 Randy Dunlap
2023-05-30 23:39 ` Randy Dunlap
2023-06-03  1:07 ` Sean Christopherson
2023-06-03  2:27   ` Randy Dunlap
2023-06-05 16:48   ` Paolo Bonzini [this message]
2023-06-13 21:58     ` Sean Christopherson

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=b75c9696-9abb-7a3f-0fb2-56af8ef21bb6@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=seanjc@google.com \
    /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®