From: Avi Kivity <avi@redhat.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: KVM <kvm@vger.kernel.org>, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: which branch of kvm.git should I do regular testing against?
Date: Thu, 24 May 2012 12:28:49 +0300 [thread overview]
Message-ID: <4FBDFF51.9030408@redhat.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A100D30F0@SHSMSX101.ccr.corp.intel.com>
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.
>
> I know next branch contains latest KVM patches.
> But I found some recent KVM patches in master branch never existed in next branch.
> And, the next branch is based on linux3.4-rc3, while master branch is based on linux3.4-rc7.
'master' contains fixes, 'next' contains updates queued for the merge
window. 'auto-next' should contain both, plus the latest upstream.
> Another question is whether the patches in next branch will be finally merged into master branch?
>
During the merge window.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-05-24 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 9:24 which branch of kvm.git should I do regular testing against? Ren, Yongjie
2012-05-24 9:28 ` Avi Kivity [this message]
2012-05-24 9:33 ` Ren, Yongjie
2012-05-24 9:45 ` Avi Kivity
2012-05-24 9:48 ` Ren, Yongjie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FBDFF51.9030408@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=yongjie.ren@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.