From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:59491)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RV3EX-0002xn-Of
	for qemu-devel@nongnu.org; Mon, 28 Nov 2011 10:35:11 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RV3EV-0004gb-IM
	for qemu-devel@nongnu.org; Mon, 28 Nov 2011 10:35:05 -0500
Received: from mx1.redhat.com ([209.132.183.28]:26805)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RV3EV-0004gV-6f
	for qemu-devel@nongnu.org; Mon, 28 Nov 2011 10:35:03 -0500
Message-ID: <4ED3AA22.1040005@redhat.com>
Date: Mon, 28 Nov 2011 17:34:58 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <87vcq4nx3d.fsf@trasno.mitica> <4ED39A82.5060501@codemonkey.ws>
	<4ED39B06.10002@redhat.com> <4ED39C33.1020904@codemonkey.ws>
In-Reply-To: <4ED39C33.1020904@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] KVM call agenda for November 29
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Developers qemu-devel <qemu-devel@nongnu.org>, KVM devel mailing list <kvm@vger.kernel.org>, quintela@redhat.com

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.

-- 
error compiling committee.c: too many arguments to function