From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Developers qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for November 29
Date: Mon, 28 Nov 2011 08:35:31 -0600 [thread overview]
Message-ID: <4ED39C33.1020904@codemonkey.ws> (raw)
In-Reply-To: <4ED39B06.10002@redhat.com>
On 11/28/2011 08:30 AM, Avi Kivity wrote:
> On 11/28/2011 04:28 PM, Anthony Liguori wrote:
>> On 11/28/2011 08:24 AM, Juan Quintela wrote:
>>>
>>> Hi
>>>
>>> Please send in any agenda items you are interested in covering.
>>
>> - 1.1 development window logistics
>
> (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.
Regards,
Anthony Liguori
>
next prev parent reply other threads:[~2011-11-28 14:35 UTC|newest]
Thread overview: 11+ 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:24 ` [Qemu-devel] " Juan Quintela
2011-11-28 14:28 ` Anthony Liguori
2011-11-28 14:30 ` Avi Kivity
2011-11-28 14:30 ` Avi Kivity
2011-11-28 14:35 ` Anthony Liguori [this message]
2011-11-28 15:34 ` Avi Kivity
2011-11-29 13:25 ` Juan Quintela
2011-11-29 13:25 ` [Qemu-devel] " Juan Quintela
2011-11-29 13:57 ` Anthony Liguori
2011-11-29 13:57 ` [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=4ED39C33.1020904@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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 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.