qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Wayne Xia <xiawenc@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/1] Make the help info more friendly in monitor
Date: Tue, 4 Oct 2011 10:55:18 -0300	[thread overview]
Message-ID: <20111004105518.3404b76a@doriath> (raw)
In-Reply-To: <CAJSP0QXjvUM0hBXLwTnRK5N6F1M+iB_77+B2mRnaZNfTfe5apQ@mail.gmail.com>

On Wed, 28 Sep 2011 10:16:19 +0100
Stefan Hajnoczi <stefanha@gmail.com> wrote:

> On Wed, Sep 28, 2011 at 10:00 AM, Wayne Xia <xiawenc@linux.vnet.ibm.com> wrote:
> > During my test, I found it inconvenient when I type "help" or "help info",
> > because the information was shown without orderliness. This patch would just
> > show the help information in sorted order.
> >
> > For eg:
> > (qemu)help
> > acl_add
> > acl_policy
> > acl_remove
> > acl_reset
> > acl_show
> > balloon
> > block_passwd
> > ...
> > the command list is sorted.
> >
> > Wayne Xia (1):
> >  Sort the help info shown in monitor
> >
> >  monitor.c |   97 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--
> >  1 files changed, 93 insertions(+), 4 deletions(-)
> 
> This is a nice idea.  We could keep hmp/qmp-commands.hx in sorted
> order but that prevents us from keeping related commands together in
> those files (and the generated documentation?).  So sorting at
> run-time makes sense.

The info help command reads from hmp-commands.hx and the info_cmds array,
I would prefer to get those sorted.

  reply	other threads:[~2011-10-04 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28  9:00 [Qemu-devel] [PATCH 0/1] Make the help info more friendly in monitor Wayne Xia
2011-09-28  9:16 ` Stefan Hajnoczi
2011-10-04 13:55   ` Luiz Capitulino [this message]
2011-10-11  7:19     ` Wayne Xia

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=20111004105518.3404b76a@doriath \
    --to=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=xiawenc@linux.vnet.ibm.com \
    /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).