From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] insane.bbclass: Make RPATH a non-fatal error
Date: Sat, 19 Feb 2011 18:19:07 -0700 [thread overview]
Message-ID: <4D606C0B.5080508@mentor.com> (raw)
In-Reply-To: <4D5FFF05.5050603@freyther.de>
On 02/19/2011 10:33 AM, Holger Freyther wrote:
> On 02/18/2011 08:26 PM, Tom Rini wrote:
>> In order to make the user experience better we now use bb.warn
>> on non-fatal QA errors and bb.error on fatal errors.
>
>
> hmm. for every binary with a bad RPATH in your distribution your product can
> get bad press very fast. I think the commit message should reflect this in a
> way that we are aware of this and don't care.
Agreed, I will update the RPATH wording when I push this. Thanks!
--
Tom Rini
Mentor Graphics Corporation
prev parent reply other threads:[~2011-02-20 1:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 19:26 [PATCH] insane.bbclass: Make RPATH a non-fatal error Tom Rini
2011-02-18 19:33 ` Khem Raj
2011-02-18 19:36 ` Tom Rini
2011-02-18 19:53 ` Denys Dmytriyenko
2011-02-18 19:54 ` Eric Bénard
2011-02-18 20:36 ` Eric Benard
2011-02-19 9:45 ` Frans Meulenbroeks
2011-02-19 11:52 ` Andreas Mueller
2011-02-19 13:26 ` Otavio Salvador
2011-02-19 16:59 ` Tom Rini
2011-02-20 12:42 ` Frans Meulenbroeks
2011-02-20 14:46 ` Tom Rini
2011-02-20 14:59 ` Eric Benard
2011-02-20 15:05 ` Andreas Mueller
2011-02-20 15:37 ` Tom Rini
2011-02-20 16:31 ` Frans Meulenbroeks
2011-02-20 16:54 ` Andreas Mueller
2011-02-20 17:56 ` Frans Meulenbroeks
2011-02-20 18:26 ` Frans Meulenbroeks
2011-02-20 18:58 ` Andreas Mueller
2011-02-19 17:33 ` Holger Freyther
2011-02-19 18:27 ` Frans Meulenbroeks
2011-02-20 1:19 ` Tom Rini [this message]
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=4D606C0B.5080508@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.