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: [XenPPC] Re: [Xen-devel] [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [XenPPC] Re: [Xen-devel] [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to support new architectures
From: Aron Griffis <aron@xxxxxx>
Date: Tue, 3 Oct 2006 12:39:45 -0400
Cc: Xen-Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Hollis Blanchard <hollisb@xxxxxxxxxx>, Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>, Ewan Mellor <ewan@xxxxxxxxxxxxx>, XenPPC-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>, Dan Smith <danms@xxxxxxxxxx>
Delivery-date: Tue, 03 Oct 2006 09:40:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1484770.1F96%Keir.Fraser@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, Hollis Blanchard <hollisb@xxxxxxxxxx>, Ewan Mellor <ewan@xxxxxxxxxxxxx>, Dan Smith <danms@xxxxxxxxxx>, Xen-Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>, XenPPC-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
References: <1159890839.2769.3.camel@xxxxxxxxxxxxxxxxxxxxx> <C1484770.1F96%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
Keir Fraser wrote:  [Tue Oct 03 2006, 11:59:28AM EDT]
> Xen-unstable is currently a staging tree for xen-3.0.3-testing. Development
> is frozen until 3.0.3-0 is released.

Hi Keir,

Why are you doing it this way?  I thought a staging tree was somewhere
you could test builds prior to moving changesets to the live tree, so
you could yank the changesets, reset the staging tree, etc. without
affecting anybody.  Shouldn't there be a separate staging tree for
xen-3.0.3-testing?  Plus if xen-unstable is staging for
xen-3.0.3-testing, then it seems like branching was pointless.

Aron

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

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