qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] qapi: Rename QMP and QGA schema files
Date: Fri, 20 Apr 2018 07:42:57 -0500	[thread overview]
Message-ID: <6cbb484e-7f75-5732-5ada-9fcd3a95d00f@redhat.com> (raw)
In-Reply-To: <87po2u1f3f.fsf@dusky.pond.sub.org>

[-- Attachment #1: Type: text/plain, Size: 2296 bytes --]

On 04/20/2018 03:01 AM, Markus Armbruster wrote:
> Eric Blake <eblake@redhat.com> writes:
> 
>> Having two files in the tree both named qapi-schema.json just adds
>> confusion.  Rename these files to {qmp,qga}-schema to make it
>> obvious which schema is in effect, and relocate qga into the common
>> qapi/ subdirectory.  Update all build rules that refer to the file
>> names, and adjust other documentation and comment references that
>> need to refer to the new file names.
>>
>> Maintainer-wise, this means that qapi/qga-schema.json continues
>> to belong to Michael as QGA maintainer, but now also notifies
>> Markus and Eric as QAPI maintainers, alongside all the other
>> QMP QAPI files, matching how other .json QAPI modules belong
>> to multiple maintainer blurbs.  Also, fix a stale reference to
>> a file removed in commit eb815e248f.
>>
>> Signed-off-by: Eric Blake <eblake@redhat.com>
> 
> We have three separate things: QAPI infrastructure, its use in QEMU
> proper, and its use in QGA.  We keep the former two in qapi/, and the
> latter in qga/.

And another thread raised the possibility of firmware.json (or
firmware.qapi, if we like patch 2) being in yet another directory.

> 
> Giving the two qapi-schema.json different names is fine with me.
> qga-schema.json is an obvious choice.  qmp-schema.json less so, because
> it's actually used for more than just QMP now.  qemu-schema.json?  Or
> just keep the old name?

qapi-schema.qapi sounds repetitive; qemu-schema.qapi seems reasonable,
if we need it.  Also, remember that we have the QMP command
'query-qmp-schema', so the name qmp-schema makes some sense, even if the
file does cover more than QMP.

> 
> Splitting qapi/ into infrastructure and use now doesn't seem to be worth
> the bother.  I'd prefer to keep the use for QGA separate, though.  The
> case for moving them together would be stronger if they shared schema
> parts.  Matter of taste, I guess, and that means it's up to the QGA
> maintainer.  Michael?
> 
> If we decide to keep them separate, but still want MAINTAINERS' QAPI
> Schema stanza to cover QGA, that's a one-liner.
> 

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2018-04-20 12:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 22:31 [Qemu-devel] [PATCH v2 0/2] QAPI file renames Eric Blake
2018-04-19 22:31 ` [Qemu-devel] [PATCH v2 1/2] qapi: Rename QMP and QGA schema files Eric Blake
2018-04-20  8:01   ` Markus Armbruster
2018-04-20 12:42     ` Eric Blake [this message]
2018-04-19 22:31 ` [Qemu-devel] [PATCH v2 2/2] qapi: Rename .json to .qapi Eric Blake
2018-04-20  8:35   ` Markus Armbruster
2018-04-20  9:27     ` Dr. David Alan Gilbert
2018-04-20 13:16       ` Eric Blake
2018-04-20  9:46   ` Dr. David Alan Gilbert

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=6cbb484e-7f75-5732-5ada-9fcd3a95d00f@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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 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).