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] 2.6.18 kernel status

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] 2.6.18 kernel status
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Tue, 6 Mar 2007 17:19:52 +0000
Cc: John Hannfield <hal9020@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 06 Mar 2007 09:19:02 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C212F2D6.AAD4%keir@xxxxxxxxxxxxx>
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: <4d95b0990703051553n7437d02etb9765d331abc0284@xxxxxxxxxxxxxx> <C212F2D6.AAD4%keir@xxxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Tue, Mar 06, 2007 at 10:28:38AM +0000, Keir Fraser wrote:
> On 5/3/07 23:53, "John Hannfield" <hal9020@xxxxxxxxx> wrote:
> > I am just trying out the 2.6.18 kernel in xen-unstable.hg , but on doing a
> > make linux-2.6-xen0-build I'm getting to the following error.
> This is fixed but the patch is stuck in our staging tree until regression
> tests pass.

How about making your staging tree publically viewable so people get better
visibility into whether patches sent to xen-devel have been picked up and
integrated into the tree ? Sure, we don't want people to be actually working
against a staging tree, but I think being able to see what's coming along
in the staging tree would be good for transparency / communications with
the non-XenSource people whom are posting patches. 

In this particular instance it would also allow for end-user testing of
the aforementioned kernel patch in parallel with the automated tests,
rather than serializing the test proces.

|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

Xen-devel mailing list