From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: which branch of kvm.git should I do regular testing against? Date: Thu, 24 May 2012 12:45:57 +0300 Message-ID: <4FBE0355.8090203@redhat.com> References: <1B4B44D9196EFF41AE41FDA404FC0A100D30F0@SHSMSX101.ccr.corp.intel.com> <4FBDFF51.9030408@redhat.com> <1B4B44D9196EFF41AE41FDA404FC0A100D3127@SHSMSX101.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: KVM , Marcelo Tosatti To: "Ren, Yongjie" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:58483 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754359Ab2EXJqB (ORCPT ); Thu, 24 May 2012 05:46:01 -0400 In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A100D3127@SHSMSX101.ccr.corp.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: On 05/24/2012 12:33 PM, Ren, Yongjie wrote: >> >> On 05/24/2012 12:24 PM, Ren, Yongjie wrote: >> > Hi Avi, >> > Our team spare some effort in regular nightly testing against KVM >> upstream. >> > We're using master branch now and all the test reports I sent out are >> based on master branch. >> > Which branch of kvm.git should we do regular testing against? >> > Your suggestion? >> >> kvm.git next. In theory kvm.git auto-next is even better, but we >> sometimes forget to update it. >> > Thanks. Get it. I'll use kvm.git next. > As for qemu-kvm.git, master or next branch? Unlike kvm.git, these should be pretty close. 'next' is untested, 'master' is tested, they are synced after testing. I suggest 'master'. -- error compiling committee.c: too many arguments to function