From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: 2.6.18 kernel status Date: Tue, 6 Mar 2007 17:19:52 +0000 Message-ID: <20070306171952.GK29872@redhat.com> References: <4d95b0990703051553n7437d02etb9765d331abc0284@mail.gmail.com> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: John Hannfield , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Mar 06, 2007 at 10:28:38AM +0000, Keir Fraser wrote: > > On 5/3/07 23:53, "John Hannfield" 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. Regards, Dan. -- |=- 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 -=|