From: Joanna Rutkowska <joanna@invisiblethingslab.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: New release candidate for Xen 4.0.0 (RC9)
Date: Wed, 31 Mar 2010 13:00:50 +0200 [thread overview]
Message-ID: <4BB32B62.4000408@invisiblethingslab.com> (raw)
In-Reply-To: <C7D8E891.F54D%keir.fraser@eu.citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 986 bytes --]
On 03/31/2010 12:54 PM, Keir Fraser wrote:
> On 31/03/2010 11:07, "Joanna Rutkowska" <joanna@invisiblethingslab.com>
> wrote:
>
>> On 03/31/2010 11:27 AM, Keir Fraser wrote:
>>> Folks,
>>>
>>> 4.0.0-rc9 is now tagged in http://xenbits.xensource.com/xen-4.0-testing.hg
>>>
>>> This is almost certainly the last RC, and will become the 4.0.0 release
>>> around the middle of next week. Please test!
>>>
>> BTW, any estimates for the Xen 3.4.3?
>
> Later in April.
BTW, on this page:
http://xenbits.xensource.com/
one can see linux-2.6.18-xen.hg repo as a sub-repo of the just-created
xen-4.0-testing.hg... I was under impression that 4.0 would be using
pvops0 kernel *only* and that you would not support 2.6.18 anymore for
this hypervisor...
Can you shed some light on this issue -- why is this kernel repo there,
and what kernel will *really* be the official and stable option for Xen
4? What will be part of the next week release?
Thanks,
joanna.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 226 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-31 11:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 9:27 New release candidate for Xen 4.0.0 (RC9) Keir Fraser
2010-03-31 10:07 ` Joanna Rutkowska
2010-03-31 10:54 ` Keir Fraser
2010-03-31 11:00 ` Joanna Rutkowska [this message]
2010-03-31 11:13 ` Keir Fraser
2010-03-31 12:38 ` Ian Pratt
2010-03-31 14:20 ` Dan Magenheimer
2010-03-31 14:32 ` Keir Fraser
2010-03-31 14:44 ` Ian Pratt
2010-03-31 19:55 ` Grant McWilliams
2010-03-31 15:02 ` Bastian Blank
2010-03-31 15:09 ` Keir Fraser
2010-03-31 15:44 ` Bastian Blank
2010-03-31 16:38 ` Keir Fraser
2010-03-31 18:03 ` Konrad Rzeszutek Wilk
2010-03-31 18:18 ` Keir Fraser
2010-03-31 20:40 ` Jeremy Fitzhardinge
2010-03-31 19:10 ` Konrad Rzeszutek Wilk
2010-03-31 19:33 ` Keir Fraser
2010-03-31 19:52 ` Konrad Rzeszutek Wilk
2010-03-31 20:07 ` Keir Fraser
2010-03-31 21:07 ` Konrad Rzeszutek Wilk
2010-05-19 12:10 ` Keir Fraser
2010-05-26 15:02 ` Konrad Rzeszutek Wilk
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=4BB32B62.4000408@invisiblethingslab.com \
--to=joanna@invisiblethingslab.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).