From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL for-2.5 0/2] QAPI patches
Date: Tue, 17 Nov 2015 09:46:34 +0100 [thread overview]
Message-ID: <1447749996-22654-1-git-send-email-armbru@redhat.com> (raw)
The following changes since commit c257779e2a586043a1480bb7e96fb6bcd0129634:
Merge remote-tracking branch 'remotes/otubo/tags/pull-seccomp-20151116' into staging (2015-11-16 12:09:47 +0000)
are available in the git repository at:
git://repo.or.cz/qemu/armbru.git tags/pull-qapi-2015-11-17
for you to fetch changes up to 513e7cdbaeec56c77e4cf26f151d7ee79f3a6be9:
input: Document why x-input-send-event is still experimental (2015-11-17 08:42:07 +0100)
----------------------------------------------------------------
QAPI patches
----------------------------------------------------------------
Eric Blake (2):
qapi: Document introspection stability considerations
input: Document why x-input-send-event is still experimental
docs/qapi-code-gen.txt | 11 +++++++++++
qapi-schema.json | 13 +++++++++++--
qapi/introspect.json | 9 +++++++++
3 files changed, 31 insertions(+), 2 deletions(-)
Eric Blake (2):
qapi: Document introspection stability considerations
input: Document why x-input-send-event is still experimental
docs/qapi-code-gen.txt | 11 +++++++++++
qapi-schema.json | 13 +++++++++++--
qapi/introspect.json | 9 +++++++++
3 files changed, 31 insertions(+), 2 deletions(-)
--
2.4.3
next reply other threads:[~2015-11-17 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 8:46 Markus Armbruster [this message]
2015-11-17 8:46 ` [Qemu-devel] [PULL for-2.5 1/2] qapi: Document introspection stability considerations Markus Armbruster
2015-11-17 8:46 ` [Qemu-devel] [PULL for-2.5 2/2] input: Document why x-input-send-event is still experimental Markus Armbruster
2015-11-17 11:33 ` [Qemu-devel] [PULL for-2.5 0/2] QAPI patches Peter Maydell
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=1447749996-22654-1-git-send-email-armbru@redhat.com \
--to=armbru@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).