This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Xen 3.4 code freeze

To: Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 3.4 code freeze
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 18 Mar 2009 15:50:54 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 18 Mar 2009 08:53:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49C122C6.76E4.0078.0@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acmn3wfI1dVbGR0bSvutSKyI4EfTYQAAkoYX
Thread-topic: [Xen-devel] Xen 3.4 code freeze
User-agent: Microsoft-Entourage/
On 18/03/2009 15:35, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

>> My plan is to take no further large feature patchsets into xen-unstable
>> until 3.4 is branched, the only exception possibly being Dan¹s tmem patches.
>> Furthermore, after Friday I¹m away for a week and when I get back I intend
>> to shake the trees into better shape and accept bug-fix patches only.
> In preparation for that, could you do a full sync of the public headers in
> the Linux tree?


 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>