Re: [Xen-devel] Daily Xen Builds

To:	Anthony Liguori <aliguori@xxxxxxxxxx>
Subject:	Re: [Xen-devel] Daily Xen Builds
From:	Dan Smith <danms@xxxxxxxxxx>
Date:	Mon, 10 Oct 2005 14:32:38 -0700
Cc:	Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Mon, 10 Oct 2005 21:30:48 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<434ADB55.8050609@xxxxxxxxxx> (Anthony Liguori's message of "Mon, 10 Oct 2005 16:21:25 -0500")
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>
References:	<1128978545.12366.15.camel@dbarrera_tp> <434ADB55.8050609@xxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux)

AL> Thoughts?

I think such a policy would definitely be beneficial to the stability
of tree.  The error in the changeset I just emailed about would have
been caught by a quick run of xm-test before commit :)

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx


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

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [Xen-devel] Daily Xen Builds, Nivedita Singhvi

Next by Date:

RE: [Xen-devel] Re: [Xen-users] xen 3.0 boot problem, Ian Pratt

Previous by Thread:

Re: [Xen-devel] Daily Xen Builds, Nivedita Singhvi

Next by Thread:

Re: [Xen-devel] Daily Xen Builds, Nicholas Lee

Indexes:

[Date] [Thread] [Top] [All Lists]

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] Daily Xen Builds