From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:40574)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R36Bp-0007hP-Oj
	for qemu-devel@nongnu.org; Mon, 12 Sep 2011 09:04:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R36Bo-0007pF-Jk
	for qemu-devel@nongnu.org; Mon, 12 Sep 2011 09:04:45 -0400
Received: from mx1.redhat.com ([209.132.183.28]:29530)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R36Bo-0007ox-Cj
	for qemu-devel@nongnu.org; Mon, 12 Sep 2011 09:04:44 -0400
Message-ID: <4E6E0368.5090207@redhat.com>
Date: Mon, 12 Sep 2011 16:04:40 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <1315824666-4214-1-git-send-email-avi@redhat.com>
	<4E6DFB29.10900@redhat.com> <4E6E01B6.10106@codemonkey.ws>
In-Reply-To: <4E6E01B6.10106@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PULL 00/28] Memory API conversion, batch 7
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: qemu-devel@nongnu.org

On 09/12/2011 03:57 PM, Anthony Liguori wrote:
> On 09/12/2011 07:29 AM, Avi Kivity wrote:
>> On 09/12/2011 01:50 PM, Avi Kivity wrote:
>>> git://github.com/avikivity/qemu.git memory/batch
>>>
>>> More of the same. I tested what I could using the images on the qemu
>>> wiki -
>>> note not all images boot even on upstream.
>>>
>>
>> Whoops - don't pull - bad patch in there.
>
> Could you adjust your script to only post a single [PULL] note and 
> then have a normal patch series with [PATCH] in the tag for the posted 
> patches?
>
> It's not terribly important, but I think it makes more sense 
> semantically and helps for anyone doing search via PATCH.  You could 
> make do [PULL][PATCH N/M] if you wanted to indicate it's a patch 
> that's part of a pull request.
>

I don't think git format-patch allows it, but it's easy to adjust the 
cover letter manually.

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