From: Meador Inge <meadori@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: riku.voipio@iki.fi
Subject: Re: [Qemu-devel] [PATCH 0/4] linux-user: Option parser cleanup
Date: Mon, 7 May 2012 09:44:09 -0500 [thread overview]
Message-ID: <4FA7DFB9.8060003@codesourcery.com> (raw)
In-Reply-To: <4F7D03C1.8050900@codesourcery.com>
Ping ^ 2.
On 04/04/2012 09:30 PM, Meador Inge wrote:
> Ping. Any comments on this series?
>
> On 03/27/2012 05:44 PM, Meador Inge wrote:
>> This series is focused at cleaning up a few issues in the
>> GNU/Linux usermode driver's option parsing. -h has been
>> fixed to exit with 0, a -help option has been added, proper
>> error messages have been added for unknown options and bad
>> arguments, and --foo is now excepted in addition to -foo.
>>
>> 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 files changed, 20 insertions(+), 10 deletions(-)
>>
>
>
--
Meador Inge
CodeSourcery / Mentor Embedded
http://www.mentor.com/embedded-software
next prev parent reply other threads:[~2012-05-07 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 22:44 [Qemu-devel] [PATCH 0/4] linux-user: Option parser cleanup Meador Inge
2012-03-27 22:44 ` [Qemu-devel] [PATCH 1/4] linux-user: Exit 0 when -h is used Meador Inge
2012-05-07 14:50 ` Andreas Färber
2012-03-27 22:44 ` [Qemu-devel] [PATCH 2/4] linux-user: Add -help Meador Inge
2012-03-27 22:44 ` [Qemu-devel] [PATCH 3/4] linux-user: Add proper error messages for bad options Meador Inge
2012-03-27 22:44 ` [Qemu-devel] [PATCH 4/4] linux-user: Treat --foo options the same as -foo Meador Inge
2012-04-05 2:30 ` [Qemu-devel] [PATCH 0/4] linux-user: Option parser cleanup Meador Inge
2012-05-07 14:44 ` Meador Inge [this message]
2012-06-08 13:40 ` Meador Inge
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=4FA7DFB9.8060003@codesourcery.com \
--to=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 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).