From: "Andreas Färber" <afaerber@suse.de>
To: Meador Inge <meadori@codesourcery.com>
Cc: riku.voipio@iki.fi, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/4] linux-user: Exit 0 when -h is used
Date: Mon, 07 May 2012 16:50:55 +0200 [thread overview]
Message-ID: <4FA7E14F.4050207@suse.de> (raw)
In-Reply-To: <1332888271-7083-2-git-send-email-meadori@codesourcery.com>
Am 28.03.2012 00:44, schrieb Meador Inge:
> Signed-off-by: Meador Inge <meadori@codesourcery.com>
> ---
> linux-user/main.c | 20 ++++++++++----------
> 1 files changed, 10 insertions(+), 10 deletions(-)
Reviewed-by: Andreas Färber <afaerber@suse.de>
/-F
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-05-07 14:51 UTC|newest]
Thread overview: 14+ 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 [this message]
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
2012-06-08 13:40 ` Meador Inge
-- strict thread matches above, loose matches on Subject: below --
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
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=4FA7E14F.4050207@suse.de \
--to=afaerber@suse.de \
--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.