From: Hani Benhabiles <kroosec@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] monitor: Command completion for various commands
Date: Tue, 20 May 2014 00:05:51 +0100 [thread overview]
Message-ID: <20140519230551.GC21461@Inspiron-3521> (raw)
In-Reply-To: <1400540468-1177-1-git-send-email-kroosec@gmail.com>
On Tue, May 20, 2014 at 12:01:01AM +0100, Hani Benhabiles wrote:
> A set of patches adding completion support for various hmp commands. Following
> other series that were merged earlier.
>
Resent the complete series. Please ignore this incomplete one.
Sorry for the flood.
> Hani Benhabiles (7):
> monitor: Add ringbuf_write and ringbuf_read argument completion.
> monitor: Add watchdog_action argument completion.
> monitor: Add migrate_set_capability completion.
> monitor: Add host_net_add device argument completion.
> readline: Make completion strings always unique.
> monitor: Add host_net_remove arguments completion.
> monitor: Add delvm and loadvm argument completion.
>
> hmp-commands.hx | 10 ++-
> hmp.h | 11 ++++
> include/sysemu/char.h | 3 +-
> monitor.c | 174 ++++++++++++++++++++++++++++++++++++++++++++++++++
> qemu-char.c | 2 +-
> util/readline.c | 6 ++
> 6 files changed, 202 insertions(+), 4 deletions(-)
>
> --
> 1.8.3.2
>
next prev parent reply other threads:[~2014-05-19 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 23:01 [Qemu-devel] monitor: Command completion for various commands Hani Benhabiles
2014-05-19 23:01 ` [Qemu-devel] [PATCH 1/7] monitor: Add ringbuf_write and ringbuf_read argument completion Hani Benhabiles
2014-05-19 23:01 ` [Qemu-devel] [PATCH 2/7] monitor: Add watchdog_action " Hani Benhabiles
2014-05-19 23:01 ` [Qemu-devel] [PATCH 3/7] monitor: Add migrate_set_capability completion Hani Benhabiles
2014-05-19 23:05 ` Hani Benhabiles [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-19 23:03 [Qemu-devel] monitor: Command completion for various commands Hani Benhabiles
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=20140519230551.GC21461@Inspiron-3521 \
--to=kroosec@gmail.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).