From: Anthony Liguori <anthony@codemonkey.ws>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: [Qemu-devel] Re: QAPI Merge Plans
Date: Tue, 08 Mar 2011 17:44:06 -0600 [thread overview]
Message-ID: <4D76BF46.5020708@codemonkey.ws> (raw)
In-Reply-To: <20110308201842.73ba7a19@doriath>
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
prev parent reply other threads:[~2011-03-08 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 20:54 [Qemu-devel] QAPI Merge Plans Anthony Liguori
2011-03-08 23:18 ` [Qemu-devel] " Luiz Capitulino
2011-03-08 23:44 ` Anthony Liguori [this message]
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=4D76BF46.5020708@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.