From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: Fwd: buildbot failure in qemu-kvm on disable_kvm_i386_centos_5_2
Date: Mon, 27 Jul 2009 12:21:06 +0300
Message-ID: <4A6D7182.4030608@redhat.com>
References: <200907261351.13161.gollub@b1-systems.de> <4A6C458E.2080601@redhat.com> <200907261414.14245.gollub@b1-systems.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Daniel Gollub <gollub@b1-systems.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:33712 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751028AbZG0JVM (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 27 Jul 2009 05:21:12 -0400
In-Reply-To: <200907261414.14245.gollub@b1-systems.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 07/26/2009 03:14 PM, Daniel Gollub wrote:
> Hi Avi,
>
> On Sunday 26 July 2009 02:01:18 pm Avi Kivity wrote:
> [...]
>    
>> Can you set up testing for the 'next' branch?  It will catch issues much
>> earlier.
>>      
>
> Actutally i thought it is. But for some reason it is not getting notified by
> the git hook. Could you ping me on IRC before you push something (only) to
> next-branch, so i can have a look at the buildbot logs ...
>    

That was broken at my end; fixed.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.