From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55584) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1asbFf-0007lY-Ds for qemu-devel@nongnu.org; Tue, 19 Apr 2016 15:24:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1asbFa-00076N-47 for qemu-devel@nongnu.org; Tue, 19 Apr 2016 15:23:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56316) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1asbFZ-00076J-Uj for qemu-devel@nongnu.org; Tue, 19 Apr 2016 15:23:54 -0400 References: <1460494796-12668-1-git-send-email-silbe@linux.vnet.ibm.com> <878u0gih1h.fsf@oc4731375738.ibm.com> <20160415153520.GI4341@noname.redhat.com> <87wpnt5shx.fsf@oc4731375738.ibm.com> From: Eric Blake Message-ID: <571685C6.3060103@redhat.com> Date: Tue, 19 Apr 2016 13:23:50 -0600 MIME-Version: 1.0 In-Reply-To: <87wpnt5shx.fsf@oc4731375738.ibm.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0lB91obEUSxUC52uO93VBnHf6Tv8k9inS" Subject: Re: [Qemu-devel] [for-2.6] Re: [PATCH] qmp-commands.hx: document minimum speed for block jobs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sascha Silbe , Kevin Wolf Cc: Markus Armbruster , qemu-devel@nongnu.org, Max Reitz This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --0lB91obEUSxUC52uO93VBnHf6Tv8k9inS Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 04/19/2016 01:05 PM, Sascha Silbe wrote: > Dear Kevin, >=20 > Kevin Wolf writes: >=20 > [...] >> Isn't the JSON schema (qapi/block-core.json) considered the >> authoritative source for interface specifications these days? I think = if >> we want to document the shortcomings for the time being, we should >> document it in both places. >=20 > Interesting. What exactly is the relationship between qmp-commands.hx > and qapi/block-core.json? Ultimately, we want to make qmp-commands.hx go away, and have everything generated from qapi/*.json. Marc-Andre has proposed some patches along those lines (back in the 2.5 timeframe, but dependent on other qapi patches that are still pending review). >=20 > At any rate, you're right that we should update both. See v2. Until we've automated the docs from a single source file, that is the correct approach. >=20 > (And I've forgot the for-2.6 prefix for the patch itself again. Bah.) >=20 > Sascha >=20 --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --0lB91obEUSxUC52uO93VBnHf6Tv8k9inS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJXFoXGAAoJEKeha0olJ0NqRNUIAJwL8V9PIrZp70ZWARdDPYZC R/gAoMoKznFFp0dx0ITJqUCwX6Lju3of7XpzMISBFrKMYRyQToRrYZOmeeJhUNDZ Rs7rhlj8s7Qvvuq7NpAU3iMdp91QGJt/Pv42fOauqKlV43ZPgG8uBdM/ALOf3hYt bNnt5ltDu1iJAOiRXFB+gXsTPLYCEvwuzaoGnj4PH/C977uwGHKaDHrobUTmsEiU JmNb5ey6O4fkKbBxxAFTUeYf5jZX+/3Y8tsYbzbbANNKYF/tAgp1I926nRNcle3g mXPG+0Ps+4x8c2slTy6b72WrFQbfc7Hb9VNHNBami80O/+oCSPM1HalqqUW/exE= =6LaU -----END PGP SIGNATURE----- --0lB91obEUSxUC52uO93VBnHf6Tv8k9inS--