From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake does not fail when QA issues encountered
Date: Fri, 04 Feb 2011 10:37:59 -0700 [thread overview]
Message-ID: <4D4C3977.8010504@mentor.com> (raw)
In-Reply-To: <AANLkTi=o+QW-K2VG7WBFFTrshxhD1TDMbqx=EbTxDj5h@mail.gmail.com>
On 02/04/2011 08:26 AM, Frans Meulenbroeks wrote:
[snip]
> And yes, I could try to fix these myself. I used to work on everything
> and tried to fix things that were left dangling, but some people in
> the community are so unforgiving and negative if you make a mistake
> (which can happen if you work on something new to you), so I basically
> gave up doing that.
> (and yes, I know if it is something you're not familiar with a patch
> can be posted to the list, but unfortunately lots of times patches
> (especially for areas that are less mainstream) the response on posted
> patches is nil).
I am very sorry you have found this to be the case. This is a problem
the project needs to address if we wish to grow and thrive.
My google-fu is weak this morning and I can't find the link to an old
LMKL post where Linus explains why sometimes it's important to very
flame very bad ideas. But I would swear that part of it also did
explain that not every single bad idea needs to receive the nuclear
treatment.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-02-04 17:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 19:37 bitbake does not fail when QA issues encountered Maupin, Chase
2011-01-25 20:58 ` Frans Meulenbroeks
2011-01-25 21:36 ` Khem Raj
2011-01-26 10:32 ` Martyn Welch
2011-01-26 15:03 ` Maupin, Chase
2011-01-26 15:27 ` Tom Rini
2011-01-27 9:38 ` Thomas Zimmermann
2011-01-27 11:27 ` Frans Meulenbroeks
2011-01-27 15:02 ` Tom Rini
2011-02-03 7:09 ` Denys Dmytriyenko
2011-02-03 17:43 ` Tom Rini
2011-02-03 22:20 ` Denys Dmytriyenko
2011-02-03 23:09 ` Tom Rini
2011-02-04 7:54 ` Frans Meulenbroeks
2011-02-04 8:16 ` Stefan Schmidt
2011-02-04 8:37 ` Frans Meulenbroeks
2011-02-04 9:03 ` Stefan Schmidt
2011-02-04 9:57 ` Frans Meulenbroeks
2011-02-04 12:42 ` Otavio Salvador
2011-02-04 13:10 ` Frans Meulenbroeks
2011-02-04 13:58 ` Andreas Mueller
2011-02-04 14:59 ` Tom Rini
2011-02-04 15:26 ` Frans Meulenbroeks
2011-02-04 15:52 ` Otavio Salvador
2011-02-05 13:35 ` Frans Meulenbroeks
2011-02-06 1:21 ` Otavio Salvador
2011-02-06 12:02 ` Frans Meulenbroeks
2011-02-09 20:02 ` Maupin, Chase
2011-02-09 20:13 ` Maupin, Chase
2011-02-10 6:32 ` Frans Meulenbroeks
2011-02-04 17:37 ` Tom Rini [this message]
2011-02-04 14:44 ` Tom Rini
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=4D4C3977.8010504@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox