From: Kevin Bowling <kevin.bowling@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC GIT PULL (late)] Xen updates for v2.6.30
Date: Thu, 09 Apr 2009 14:35:33 -0700 [thread overview]
Message-ID: <grlpna$3sq$1@ger.gmane.org> (raw)
In-Reply-To: 20090409181039.GA605@elte.hu
Ingo Molnar wrote:
> Linus,
>
> Would you still be willing to pull pending Xen updates? They can be
> pulled from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
> xen-for-linus
>
> These are late, delayed past the merge window due to the discussions
> around the DOM0 bits and due to an exceptionally busy merge window.
There are a lot of us that would really like to see Xen dom0 merged
upstream, and several people were disappointed when it didn't go in the
2.6.30-rc1 merge window (check that thread). The biggest concern was "do
people _want_ Xen merged?" rather than any technical problems with the code.
I think, without a doubt, yes. Xen is used by many corporations. It has
excellent performance, works across platforms that do not have hardware
virt, and has a proven track record -- check out companies like Linode.com
and Slicehost. It also has the maintainership of Citrix, so it is unlikely
that the code will stagnate or become a burden to other maintainers.
Since the state of Xen dom0 was not addressed in the 2.6.30-rc1 thread,
please state your intentions here.
Regards,
Kevin
next prev parent reply other threads:[~2009-04-09 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 18:10 [RFC GIT PULL (late)] Xen updates for v2.6.30 Ingo Molnar
2009-04-09 21:35 ` Kevin Bowling [this message]
2009-04-10 1:19 ` Morten P.D. Stevens
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='grlpna$3sq$1@ger.gmane.org' \
--to=kevin.bowling@gmail.com \
--cc=linux-kernel@vger.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 NNTP newsgroup(s).