From: Laurent Vivier <laurent@vivier.eu>
To: meadori@codesourcery.com, qemu-devel@nongnu.org
Cc: riku.voipio@iki.fi
Subject: Re: [Qemu-devel] [PATCH 0/4] linux-user: CLI cleanup
Date: Mon, 6 Jul 2015 21:59:44 +0200 [thread overview]
Message-ID: <559ADE30.5060103@vivier.eu> (raw)
In-Reply-To: <1436205821-20320-1-git-send-email-meadori@codesourcery.com>
Le 06/07/2015 20:03, meadori@codesourcery.com a écrit :
> From: Meador Inge <meadori@codesourcery.com>
>
> This patch series fixes a few nits in the Linux
> usermode driver to make the general behavior less
> surprising (proper error codes, --foo options, and
> -help) and to make it easier to discover bad command
> line input.
>
> Meador Inge (4):
> linux-user: Exit 0 when -h is used
> linux-user: Add -help
> linux-user: Add proper error messages for bad options
> linux-user: Treat --foo options the same as -foo
>
> linux-user/main.c | 30 ++++++++++++++++++++----------
> 1 file changed, 20 insertions(+), 10 deletions(-)
>
Perhaps it is time to switch to getopt_long() ?
(We could manage environment variable in second array).
Riku, your opinion ?
Laurent
next prev parent reply other threads:[~2015-07-06 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 18:03 [Qemu-devel] [PATCH 0/4] linux-user: CLI cleanup meadori
2015-07-06 18:03 ` [Qemu-devel] [PATCH 1/4] linux-user: Exit 0 when -h is used meadori
2015-07-06 19:43 ` Laurent Vivier
2015-07-08 20:02 ` Meador Inge
2015-07-13 20:08 ` Meador Inge
2015-09-28 13:22 ` Riku Voipio
2015-07-06 18:03 ` [Qemu-devel] [PATCH 2/4] linux-user: Add -help meadori
2015-07-06 18:03 ` [Qemu-devel] [PATCH 3/4] linux-user: Add proper error messages for bad options meadori
2015-07-06 18:03 ` [Qemu-devel] [PATCH 4/4] linux-user: Treat --foo options the same as -foo meadori
2015-07-06 19:59 ` Laurent Vivier [this message]
2015-09-28 13:15 ` [Qemu-devel] [PATCH 0/4] linux-user: CLI cleanup Riku Voipio
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=559ADE30.5060103@vivier.eu \
--to=laurent@vivier.eu \
--cc=meadori@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.