All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: {RFC] console-image.bb
Date: Wed, 17 Feb 2010 11:29:43 -0800	[thread overview]
Message-ID: <4B7C43A7.8010201@balister.org> (raw)
In-Reply-To: <hlhcpu$nn$1@ger.gmane.org>

On 02/17/2010 10:33 AM, Rolf Leggewie wrote:
> Koen Kooi wrote:
>> of all the ways to solve it, you just had to go out of your way to annoy
>> people.
>
> I thought that was your specialty.  Everybody agreed on this, except
> you, for IMHO very incomprehensible reasons.
>
> Now, people are going out of their way to please you little princess,
> address your silly concerns and you're still not satisfied.
>
> First, you complain about the image not having the angstrom- prefix
> anymore.  Now, when that's reinstated you complain again and revert a
> meaningful patch back to before its broken state.  Maybe it's time to
> check your mental state?
>
> I hope OE can soon find a way to finally end your dictatorship ways.  OE
> has been held hostage to you and Angstrom for far too long.

Slow down guys, you are spinning out of control. The problem is not so 
much the change, just the silent method in which it was accomplished.

The basic problem here is that console-image is used by a variety of 
people. We do not like the name of the var for adding extra packages, 
but we use it anyway.

If this change was not reverted, I had the potential of losing lots of 
build time because of a silent change. Right now, I am working at a 
customer site and am not closely following the irc channel, so the only 
way I have of keeping up with things is on the mailing list.

Rolf, yes, this change has been flogged to death over the years, but you 
need to be more careful when making changes that impact a large 
audience. If in doubt send a patch to the list.

Personally, I would be happier just adding back the Angstrom var so 
peoples stuff didn't break and nag them to change it before removing the 
Angstrom var. But the I tend to take non-confrontational approach to 
solving problems. And this sets me up for constantly fixing other 
peoples bad commits.

Philip



  reply	other threads:[~2010-02-17 19:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-30 10:35 {RFC] console-image.bb Frans Meulenbroeks
2010-01-30 10:47 ` Rolf Leggewie
2010-01-30 10:53   ` Frans Meulenbroeks
2010-01-30 12:24     ` Michael 'Mickey' Lauer
2010-01-30 14:26   ` Philip Balister
2010-02-17 18:20   ` Koen Kooi
2010-02-17 18:33     ` Rolf Leggewie
2010-02-17 19:29       ` Philip Balister [this message]
2010-02-18 12:35         ` Rolf Leggewie
2010-02-17 18:58     ` Frans Meulenbroeks
2010-02-17 19:12       ` Koen Kooi
2010-02-17 19:40         ` Frans Meulenbroeks
2010-02-17 19:47           ` Koen Kooi
2010-02-17 19:52             ` Frans Meulenbroeks
2010-02-18  9:18         ` Frans Meulenbroeks
2010-02-18  9:42           ` Koen Kooi
2010-02-18 10:11             ` Frans Meulenbroeks
2010-02-18 11:08               ` Koen Kooi
2010-02-18 11:34                 ` Frans Meulenbroeks
2010-02-18 12:38             ` Rolf Leggewie
2010-02-18 13:47               ` Richard Purdie
2010-01-30 15:23 ` Koen Kooi
2010-01-30 15:37   ` Paul Menzel
2010-01-30 16:35     ` Koen Kooi
2010-01-30 16:54       ` Michael 'Mickey' Lauer

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=4B7C43A7.8010201@balister.org \
    --to=philip@balister.org \
    --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.