From mboxrd@z Thu Jan  1 00:00:00 1970
From: Aron Griffis <aron@hp.com>
Subject: Re: [XenPPC] Re: [PATCH 0/6][TOOLS][XM-TEST] [v2] Update
	xm-test to support new architectures
Date: Tue, 3 Oct 2006 12:39:45 -0400
Message-ID: <20061003163945.GC9217@fc.hp.com>
References: <1159890839.2769.3.camel@basalt.austin.ibm.com>
	<C1484770.1F96%Keir.Fraser@cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <C1484770.1F96%Keir.Fraser@cl.cam.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen-Devel <xen-devel@lists.xensource.com>, Hollis Blanchard <hollisb@us.ibm.com>, Tony Breeds <tony@bakeyournoodle.com>, Ewan Mellor <ewan@xensource.com>, XenPPC-devel <xen-ppc-devel@lists.xensource.com>, Dan Smith <danms@us.ibm.com>
List-Id: xen-devel@lists.xenproject.org

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