From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] makedevs: rectify the exit codes and handle the invalid parameter
Date: Wed, 25 Sep 2013 15:55:10 +0100 [thread overview]
Message-ID: <1380120910.18603.333.camel@ted> (raw)
In-Reply-To: <CAMKF1srAiBKPz15vALjs-X+pZojUq=y=zGeoAj1zj-s-oHQW6w@mail.gmail.com>
On Wed, 2013-09-25 at 07:27 -0700, Khem Raj wrote:
> On Tuesday, September 24, 2013, wrote:
> From: Roy Li <rongqing.li@windriver.com>
>
> It is correct behaviours to output help and version
> information,
> and should return 0;
> When input parameter is invalid, print help information and
> exit.
>
> This can cause gripes for systems who have scripted the old behavior
> And since it's a user visible change I would suggest to get it
> accepted upstream before
> It's applied in openembedded
>
I think we have our own copy of this particular C file so we are the
upstream...
Cheers,
Richard
next prev parent reply other threads:[~2013-09-25 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 5:58 [PATCH] makedevs: rectify the exit codes and handle the invalid parameter rongqing.li
2013-09-25 14:27 ` Khem Raj
2013-09-25 14:55 ` Richard Purdie [this message]
2013-09-25 15:50 ` Khem Raj
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=1380120910.18603.333.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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