From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: mdroth@linux.vnet.ibm.com, eblake@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] qapi: Improve qobject input visitor error reporting
Date: Tue, 21 Feb 2017 12:00:57 +0100 [thread overview]
Message-ID: <1487674859-26249-1-git-send-email-armbru@redhat.com> (raw)
The improvement is nice for QMP, but my real motivation is to avoid
embarrassingly horrible error messages for command line options once
we use the qobject input visitor there, as we do in "[PATCH RFC v2
0/2] block: Crude initial implementation of -blockdev".
Markus Armbruster (2):
qapi: Clean up after commit 3d344c2
qapi: Improve qobject input visitor error reporting
include/qapi/visitor.h | 6 --
qapi/qobject-input-visitor.c | 133 +++++++++++++++++++++++++++++--------------
2 files changed, 90 insertions(+), 49 deletions(-)
--
2.7.4
next reply other threads:[~2017-02-21 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 11:00 Markus Armbruster [this message]
2017-02-21 11:00 ` [Qemu-devel] [PATCH 1/2] qapi: Clean up after commit 3d344c2 Markus Armbruster
2017-02-21 15:59 ` Eric Blake
2017-02-21 11:00 ` [Qemu-devel] [PATCH 2/2] qapi: Improve qobject input visitor error reporting Markus Armbruster
2017-02-21 16:10 ` Eric Blake
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=1487674859-26249-1-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=eblake@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).