kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	qemu-devel@nongnu.org,
	"KVM devel mailing list" <kvm@vger.kernel.org>,
	"Juan Quintela" <quintela@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesda, August 28th
Date: Tue, 28 Aug 2012 11:27:07 -0300	[thread overview]
Message-ID: <20120828142707.GD6223@otherpad.lan.raisama.net> (raw)
In-Reply-To: <CAFEAcA8DVECZqi7mu5VzP7uds5YmUMVEOgO+4BMv6dPV=0XtQQ@mail.gmail.com>

On Tue, Aug 28, 2012 at 02:55:56PM +0100, Peter Maydell wrote:
> On 28 August 2012 14:30, Eduardo Habkost <ehabkost@redhat.com> wrote:
> > - 1.2 branching, or creation of a "cpu-next" tree where "good to be
> >   merged" patches can live until 1.2 is done;
> 
> With 1.3 due for release in just over a week, it seems unlikely
> that it's worth branching at this point...

Well, the closer to the release, the smaller the cost of branching as we
won't have many patches entering the 1.2 branch, anyway.

But in the end, this is more a problem of patch review capacity, than
about having a branch created. One can easily create a branch somewhere
(I am going to create a "cpu-next" branch for the patches that seem to
be "ready to go"), and propose to get it merged after 1.2 is out. But
the problem is to have enough eyeballs to look at it to decide if each
patch should go into that branch, or not.

-- 
Eduardo

  reply	other threads:[~2012-08-28 14:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 22:54 KVM call agenda for Tuesda, August 28th Juan Quintela
2012-08-28 13:30 ` Eduardo Habkost
2012-08-28 13:43   ` Juan Quintela
2012-08-28 13:48     ` [Qemu-devel] " Eduardo Habkost
2012-08-28 13:55   ` Peter Maydell
2012-08-28 14:27     ` Eduardo Habkost [this message]
2012-08-28 17:59       ` [Qemu-devel] " Andreas Färber
2012-08-28 18:03         ` Eduardo Habkost
2012-08-28 19:15           ` Anthony Liguori
2012-08-28 19:28             ` Eduardo Habkost
2012-08-28 19:59               ` [Qemu-devel] " Anthony Liguori

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=20120828142707.GD6223@otherpad.lan.raisama.net \
    --to=ehabkost@redhat.com \
    --cc=afaerber@suse.de \
    --cc=imammedo@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).