From: Bandan Das <bsd@redhat.com>
To: qemu-devel@nongnu.org
Cc: armbru@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] monitor: suggest running "help" for command errors
Date: Tue, 26 May 2015 19:45:15 -0400 [thread overview]
Message-ID: <1432683917-19906-1-git-send-email-bsd@redhat.com> (raw)
v2:
Split up the command name and arguments parsing into
separate functions. [1/2]
Skip checking for failures with commands that use the .cmd_new
interface or the async interface since they are scheduled
for removal [2/2]
Bandan Das (2):
monitor: cleanup parsing of cmd name and cmd arguments
monitor: suggest running "help" for command errors
monitor.c | 86 +++++++++++++++++++++++++++++++++++++++------------------------
1 file changed, 53 insertions(+), 33 deletions(-)
--
2.1.0
next reply other threads:[~2015-05-26 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 23:45 Bandan Das [this message]
2015-05-26 23:45 ` [Qemu-devel] [PATCH v2 1/2] monitor: cleanup parsing of cmd name and cmd arguments Bandan Das
2015-05-27 8:10 ` Markus Armbruster
2015-05-26 23:45 ` [Qemu-devel] [PATCH v2 2/2] monitor: suggest running "help" for command errors Bandan Das
2015-05-27 8:11 ` 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=1432683917-19906-1-git-send-email-bsd@redhat.com \
--to=bsd@redhat.com \
--cc=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).