From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=46496 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Px6ZZ-0005Op-Fq
	for qemu-devel@nongnu.org; Tue, 08 Mar 2011 18:44:14 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Px6ZY-00015T-DG
	for qemu-devel@nongnu.org; Tue, 08 Mar 2011 18:44:13 -0500
Received: from mail-iw0-f173.google.com ([209.85.214.173]:46834)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Px6ZY-00015I-72
	for qemu-devel@nongnu.org; Tue, 08 Mar 2011 18:44:12 -0500
Received: by iwl42 with SMTP id 42so6499673iwl.4
	for <qemu-devel@nongnu.org>; Tue, 08 Mar 2011 15:44:11 -0800 (PST)
Message-ID: <4D76BF46.5020708@codemonkey.ws>
Date: Tue, 08 Mar 2011 17:44:06 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
References: <4D73F49D.9010001@codemonkey.ws> <20110308201842.73ba7a19@doriath>
In-Reply-To: <20110308201842.73ba7a19@doriath>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: QAPI Merge Plans
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/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: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Markus Armbruster <armbru@redhat.com>

On 03/08/2011 05:18 PM, Luiz Capitulino wrote:
> On Sun, 06 Mar 2011 14:54:53 -0600
> Anthony Liguori<anthony@codemonkey.ws>  wrote:
>
>> Hi,
>>
>> I've gotten my QAPI branch now functionally complete so I'm ready to
>> start working on merging.  I thought I'd send a note about my plans as
>> both a heads up and to see if anyone had any suggestions.
>>
>> My plan is to split everything up into three rounds.  The first round
>> will just be core infrastructure--the code generator, the new QMP
>> server, the signal infrastructure, etc.  This round will introduce a new
>> command line option to expose the new QMP server (still chardev based).
> This means current-to-be-replaced infrastructure is still available?

Yes.

>   I'd
> like to avoid having two (public) QMPs if possible, even temporary.

It's unavoidable unless we're going to try and review and merge a huge 
number of patches at once.  If we do that, nothing's going to get 
reviewed properly and I want to avoid another qdev-style merge and then 
ask for forgiveness afterwards :-)

I'm not hugely opposed to just not merging the -qmp2 flag but I don't 
really see it as a bad thing.  -qmp2 disappears once round two is merged 
and round 2 should be very easy to merge once round 1 is merged.

The command conversion is extremely straight forward minus some of the 
qdev error propagation changes.

Regards,

Anthony Liguori