From: Juan Quintela <quintela@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
Developers qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: KVM call agenda for November 29
Date: Tue, 29 Nov 2011 14:25:32 +0100 [thread overview]
Message-ID: <87ehwrnjqr.fsf@trasno.mitica> (raw)
In-Reply-To: <4ED3AA22.1040005@redhat.com> (Avi Kivity's message of "Mon, 28 Nov 2011 17:34:58 +0200")
Avi Kivity <avi@redhat.com> wrote:
> On 11/28/2011 04:35 PM, Anthony Liguori wrote:
>>> (somewhat related) memory API conversion queue merge plan
>>
>>
>> No need to wait until tomorrow to discuss it, I guess.
>>
>> 1.1 will open up on Friday. I was going to make the suggestion that
>> if anyone has more than 50 non-trivial patches queued in their trees
>> (I suspect a few people do), they split up the pull requests into ~50
>> or so chunks and send them with a week or so spacing.
>>
>> 50 is just a random number. Just split the requests into reasonable
>> chunks so master doesn't totally fall apart all at once :-)
>>
>> I think memory API may be a special case since a lot of the changes
>> are trivial. So I would expect a larger pull request for the memory
>> API bits.
>
> Yes, for the memory API conversion I'd like use 126 patch chunks. While
> there are probably a few regressions lurking in there, it's easily
> bisectable and fixable. Better in than out.
Bad boy, you should use 128 patchs chunks O:-)
I have the vmstate cpus conversion done, and for Friday would have
something about virtio conversion.
Later, Juan.
next prev parent reply other threads:[~2011-11-29 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 14:24 KVM call agenda for November 29 Juan Quintela
2011-11-28 14:28 ` [Qemu-devel] " Anthony Liguori
2011-11-28 14:30 ` Avi Kivity
2011-11-28 14:35 ` Anthony Liguori
2011-11-28 15:34 ` Avi Kivity
2011-11-29 13:25 ` Juan Quintela [this message]
2011-11-29 13:57 ` 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=87ehwrnjqr.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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