From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: lcapitulino@redhat.com, Amos Kong <akong@redhat.com>,
qemu-devel@nongnu.org, stefanha@redhat.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/3] qapi.py: Allow top-level type reference for command definitions
Date: Fri, 21 Jun 2013 12:12:59 +0100 [thread overview]
Message-ID: <51C4353B.40606@redhat.com> (raw)
In-Reply-To: <20130621110024.GE2986@dhcp-200-207.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
On 06/21/2013 12:00 PM, Kevin Wolf wrote:
>> As the .json file gets larger, I've been wondering if
>> enforcing alphabetical ordering would make it easier to manage; but if
>> topological sorting is required, alphabetical sorting might not always
>> be possible.
>
> Yeah, possibly. Another thing I was considering is introducing include
> files, so that I could for example specify { 'include':
> 'block/qapi-schema.json' } and have all block-related things separated
> in this file.
Patches for include files have already been proposed:
https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg04078.html
Maybe it's worth isolating that from its larger (and now abandoned?)
series into an independent smaller series?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-06-21 11:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 16:28 [Qemu-devel] [PATCH 0/3] qapi: Top-level type reference for command definitions Kevin Wolf
2013-06-19 16:28 ` [Qemu-devel] [PATCH 1/3] qapi.py: Move common code to evaluate() Kevin Wolf
2013-06-21 16:39 ` mdroth
2013-06-24 15:17 ` Kevin Wolf
2013-06-24 16:06 ` mdroth
2013-06-19 16:28 ` [Qemu-devel] [PATCH 2/3] qapi.py: Allow top-level type reference for command definitions Kevin Wolf
2013-06-21 10:30 ` Eric Blake
2013-06-21 11:00 ` Kevin Wolf
2013-06-21 11:12 ` Eric Blake [this message]
2013-06-19 16:28 ` [Qemu-devel] [PATCH 3/3] qapi-schema: Use BlockdevSnapshot type for blockdev-snapshot-sync Kevin Wolf
2013-06-21 10:31 ` Eric Blake
2013-06-21 15:10 ` Luiz Capitulino
2013-06-20 7:43 ` [Qemu-devel] [PATCH 0/3] qapi: Top-level type reference for command definitions Stefan Hajnoczi
2013-06-21 10:31 ` Eric Blake
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=51C4353B.40606@redhat.com \
--to=eblake@redhat.com \
--cc=akong@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).