From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:38661) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RV2Iz-0007iT-8Z for qemu-devel@nongnu.org; Mon, 28 Nov 2011 09:35:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RV2Iy-0002Jm-4P for qemu-devel@nongnu.org; Mon, 28 Nov 2011 09:35:37 -0500 Received: from mail-iy0-f173.google.com ([209.85.210.173]:53203) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RV2Ix-0002Jh-Vt for qemu-devel@nongnu.org; Mon, 28 Nov 2011 09:35:36 -0500 Received: by iakk32 with SMTP id k32so10245024iak.4 for ; Mon, 28 Nov 2011 06:35:35 -0800 (PST) Message-ID: <4ED39C33.1020904@codemonkey.ws> Date: Mon, 28 Nov 2011 08:35:31 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <87vcq4nx3d.fsf@trasno.mitica> <4ED39A82.5060501@codemonkey.ws> <4ED39B06.10002@redhat.com> In-Reply-To: <4ED39B06.10002@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] KVM call agenda for November 29 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Developers qemu-devel , KVM devel mailing list , quintela@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 >