WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xen-4.1-testing branched from xen-unstable; xen-unstable

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xen-4.1-testing branched from xen-unstable; xen-unstable unfrozen
From: Shriram Rajagopalan <rshriram@xxxxxxxxx>
Date: Fri, 4 Mar 2011 11:07:40 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 04 Mar 2011 11:08:52 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19825.9812.155460.948089@xxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <19825.9812.155460.948089@xxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: rshriram@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Mar 4, 2011 at 9:50 AM, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> Following consultations, we have just branched for the Xen 4.1
> release.
>
> The new tree xen-4.1-testing.hg (and qemu-xen-4.1-testing.git) are for
> the upcoming Xen 4.1 release, and remain frozen.
>
Are there any "acked" patches that are yet to be committed into this tree?
Daniel re-acked the blktap2 patch yesterday
'blktap2: fix gap in tapdisk2 disk_type numbering' but hasnt gone into
4.1-testing.

shriram
> xen-unstable.hg and qemu-xen-unstable.git are now open for changes
> targeting Xen 4.2 and later.
>
> Until the 4.1 release takes place, please indicate when submitting
> patches which branch your patch is intended for.
>
> Ian.
>
> PS: The branching process is quite complex.  I have a checklist but it
> is possible that something is missing from it or that checklist items
> have bitrotted or that I have made error(s).  So if anything seems
> wrong please let me know.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel