xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: New release candidates for Xen 3.4.3 and 4.0.0
Date: Thu, 04 Mar 2010 10:26:37 -0800	[thread overview]
Message-ID: <4B8FFB5D.80803@goop.org> (raw)
In-Reply-To: <20100304082731.GQ2761@reaktio.net>

On 03/04/2010 12:27 AM, Pasi Kärkkäinen wrote:
> On Mon, Mar 01, 2010 at 04:57:42PM +0000, Keir Fraser wrote:
>    
>> Folks,
>>
>> New release candidates are available:
>> http://xenbits.xensource.com/xen-3.4-testing.hg (tag 3.4.3-rc3)
>> http://xenbits.xensource.com/xen-unstable.hg (tag 4.0.0-rc5)
>>
>> Please test! I think both of these are pretty close to final now.
>>
>>      
> Hello,
>
> Are you planning to switch the default in xen-unstable from 'xen/master'
> xen.git branch to xen/stable, or perhaps xen/stable-2.6.32.x ?

I want to get ACPI power management into .32 before doing that, or we'll 
be dealing with lots of regression reports.

     J

  reply	other threads:[~2010-03-04 18:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 16:57 New release candidates for Xen 3.4.3 and 4.0.0 Keir Fraser
2010-03-01 22:41 ` Mapping guest physical addresses to guest virtual addresses Abhinav Srivastava
2010-03-04  8:27 ` New release candidates for Xen 3.4.3 and 4.0.0 Pasi Kärkkäinen
2010-03-04 18:26   ` Jeremy Fitzhardinge [this message]
2010-03-23  9:49     ` xen/stable-2.6.32.x features / netchannel2 Pasi Kärkkäinen
2010-03-23 16:56       ` Jeremy Fitzhardinge
2010-03-23 20:43         ` Jeremy Fitzhardinge
2010-03-23 20:48           ` Pasi Kärkkäinen

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=4B8FFB5D.80803@goop.org \
    --to=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.com \
    --cc=pasik@iki.fi \
    --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).