From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52397) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpzH9-0001Yu-Kh for qemu-devel@nongnu.org; Fri, 21 Jun 2013 07:13:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UpzH5-0002oL-2p for qemu-devel@nongnu.org; Fri, 21 Jun 2013 07:13:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:23229) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpzH4-0002oH-QU for qemu-devel@nongnu.org; Fri, 21 Jun 2013 07:13:03 -0400 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r5LBD2YJ030202 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 21 Jun 2013 07:13:02 -0400 Message-ID: <51C4353B.40606@redhat.com> Date: Fri, 21 Jun 2013 12:12:59 +0100 From: Eric Blake MIME-Version: 1.0 References: <1371659287-14331-1-git-send-email-kwolf@redhat.com> <1371659287-14331-3-git-send-email-kwolf@redhat.com> <51C42B2A.6040607@redhat.com> <20130621110024.GE2986@dhcp-200-207.str.redhat.com> In-Reply-To: <20130621110024.GE2986@dhcp-200-207.str.redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="----enig2MIWBOHFNBTAQDQRFIRAH" Subject: Re: [Qemu-devel] [PATCH 2/3] qapi.py: Allow top-level type reference for command definitions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: lcapitulino@redhat.com, Amos Kong , qemu-devel@nongnu.org, stefanha@redhat.com, armbru@redhat.com This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2MIWBOHFNBTAQDQRFIRAH Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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. >=20 > 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? --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org ------enig2MIWBOHFNBTAQDQRFIRAH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJRxDU7AAoJEKeha0olJ0Nqyc0IAI2vTXiQMQvi1tRPp3fNokIj QqdQQ+FDihR2/hLNvU+NW8FH2lkWyI4YVqHbzZJTuMPuaF42i3CwQ5X/mXr7SYmL AJpQXiiA1lsybxtoCX/11zM+TTLtmkFV9/e2Gga3Bro5Q275RgKl4j5hyZTZ9cz7 q7I01WopNVF+am4MXxpCgm2XKifCxnAOG9812ENfjE9WKBAm1HvF569LPAUt6IUt EVZHdorMa1zkSJ6YfveSrvB/XSRDd7p6ULKcOyQetUs1oimcWKuwWusvewx+Umsk MpjbGleo4thBvlxcJEIFX+hhIeSqgeCepSi+73AggIsOamUJECWR0KU8eH1+MrM= =CyUK -----END PGP SIGNATURE----- ------enig2MIWBOHFNBTAQDQRFIRAH--