From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: armbru@redhat.com, kraxel@redhat.com
Subject: [Qemu-devel] [PATCH for-2.5 0/2] Promote 'input-send-event' to supported
Date: Wed, 11 Nov 2015 14:57:06 -0700 [thread overview]
Message-ID: <1447279028-2114-1-git-send-email-eblake@redhat.com> (raw)
Now that we have introspection, we should consider what we
are exposing to the end user, and try to avoid spurious changes
in future versions. There has been debate about switching the
qapi code generator to produce different output for 'CamelCase'
enum values; the easiest way to ensure this doesn't bite us in
later releases is to rename the QMP spellings now in a way that
doesn't impact the C spelling. Promoting the experimental
command to supported will be the easiest way to learn about the
switch in spelling.
This isn't quite a bug fix, and it won't hurt us if we delay to
2.6 (the command remains expermental for one more release). But
delaying will let the churn show up in introspection results,
so I'm arguing that it would be nice to get this series into 2.5;
even though any proposed changes to the generator won't go into
effect until 2.6.
Eric Blake (2):
input: Avoid CamelCase in InputEvent enums
input: Promote 'input-send-event' to stable API
qapi-schema.json | 14 ++++++--------
qmp-commands.hx | 24 +++++++++++-------------
ui/input.c | 4 ++--
3 files changed, 19 insertions(+), 23 deletions(-)
--
2.4.3
next reply other threads:[~2015-11-11 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 21:57 Eric Blake [this message]
2015-11-11 21:57 ` [Qemu-devel] [PATCH for-2.5 1/2] input: Avoid CamelCase in InputEvent enums Eric Blake
2015-11-12 8:23 ` Markus Armbruster
2015-11-12 13:24 ` Eric Blake
2015-11-11 21:57 ` [Qemu-devel] [PATCH for-2.5 2/2] input: Promote 'input-send-event' to stable API Eric Blake
2015-11-12 8:23 ` Markus Armbruster
2015-11-12 9:09 ` Gerd Hoffmann
2015-11-12 11:10 ` Markus Armbruster
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=1447279028-2114-1-git-send-email-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.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).