From: Luiz Capitulino <lcapitulino@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: armbru@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3 0/3] qapi: Top-level type reference for command definitions
Date: Mon, 8 Jul 2013 13:37:31 -0400 [thread overview]
Message-ID: <20130708133731.030655b6@redhat.com> (raw)
In-Reply-To: <1372689112-8093-1-git-send-email-kwolf@redhat.com>
On Mon, 1 Jul 2013 16:31:49 +0200
Kevin Wolf <kwolf@redhat.com> wrote:
> v2:
> - Updated documentation in patch 3
>
> v3:
> - Refactored differently (introduced get_expr()) as suggested by Michael
>
> Kevin Wolf (3):
> qapi.py: Avoid code duplication
> qapi.py: Allow top-level type reference for command definitions
> qapi-schema: Use BlockdevSnapshot type for blockdev-snapshot-sync
Applied to the qmp branch, thanks.
Can you post an incremental patch to cover the drive-backup command
as suggested by Eric?
>
> qapi-schema.json | 14 ++------------
> scripts/qapi.py | 37 ++++++++++++++++++++++++++++---------
> 2 files changed, 30 insertions(+), 21 deletions(-)
>
next prev parent reply other threads:[~2013-07-08 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 14:31 [Qemu-devel] [PATCH v3 0/3] qapi: Top-level type reference for command definitions Kevin Wolf
2013-07-01 14:31 ` [Qemu-devel] [PATCH v3 1/3] qapi.py: Avoid code duplication Kevin Wolf
2013-07-01 16:21 ` Michael Roth
2013-07-01 14:31 ` [Qemu-devel] [PATCH v3 2/3] qapi.py: Allow top-level type reference for command definitions Kevin Wolf
2013-07-01 16:27 ` Michael Roth
2013-07-01 14:31 ` [Qemu-devel] [PATCH v3 3/3] qapi-schema: Use BlockdevSnapshot type for blockdev-snapshot-sync Kevin Wolf
2013-07-01 16:31 ` Michael Roth
2013-07-02 19:57 ` Eric Blake
2013-07-08 17:37 ` Luiz Capitulino [this message]
2013-07-09 8:06 ` [Qemu-devel] [PATCH v3 0/3] qapi: Top-level type reference for command definitions Kevin Wolf
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=20130708133731.030655b6@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.