All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rod Whitby" <rod@whitby.id.au>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe-commits] org.oe.dev conf/*: remove all MACHINE_TASK_PROVIDER definitions that were simply forcibly defining it to the	default value set in bitbake.conf. Approved by hrw and RP.
Date: 17 Apr 2007 07:14:00 +0930	[thread overview]
Message-ID: <3259638856.300263@mail.messagingengine.com> (raw)

Apologies Koen, I thought that the positive response from hrw and RP on the -devel mailing list for making the change globally (and the lack of objections from anyone to their comments saying to go and do it) was enough.
Should I have negotiated one on one with every machine maintainer too?  If that is the case, then I simply wouldn't have bothered doing the change at all - what do I care if other distro and machine maintainers would rather do all their own cleanup?  What do I care if historical cruft builds up in OE?
This type of response to a helpful change to OE is *exactly* why I (and I expect others too) prefer to create a new distro for stuff instead of using Angstrom distro directly - it's just no fun being part of someone else's draconian fiefdom (Angstrom distro with Koen as the overlord) as opposed to being part of a group-maintained distro where positive changes are appreciated when approval of changes that bring improvements and cleanup are sought globally (as was done in this case).
-- Rod
(Apologies for formatting, sent on the road from Treo650)

-----Original Message-----
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
Date: Sunday, Apr 15, 2007 4:57 pm
Subject: Re: [oe] [oe-commits] org.oe.dev conf/*: remove all   MACHINE_TASK_PROVIDER definitions that were simply forcibly defining it to   the	default value set in bitbake.conf. Approved by hrw and RP.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

rwhitby commit schreef:
 conf/*: remove all MACHINE_TASK_PROVIDER definitions that were simply forcibly defining it to the default value set in bitbake.conf.  Approved by hrw and RP.
 
 Author: rwhitby@nslu2-linux.org

> conf/distro/include/angstrom.inc

Could you please consult with the distro maintainers before making such changes next time? The line was left in there to fix angstrom for people with a bogus MACHINE_TASK_PROVIDER entry in their local.conf.
OTOH, people now get what they deserve now when putting bogus entries in local.conf :)

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGIdPOMkyGM64RGpERAgKrAKCupbjJDnWTtoaTTBjuMueZH5kznwCggqkl
MdRJ7LalRiiqwU6I9rlCK4M=
=Yvo4
-----END PGP SIGNATURE-----

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel






             reply	other threads:[~2007-04-16 21:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16 21:44 Rod Whitby [this message]
     [not found] <E1HcvOy-0006EN-Bi@linuxtogo.org>
2007-04-15  7:27 ` [oe-commits] org.oe.dev conf/*: remove all MACHINE_TASK_PROVIDER definitions that were simply forcibly defining it to the default value set in bitbake.conf. Approved by hrw and RP Koen Kooi

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=3259638856.300263@mail.messagingengine.com \
    --to=rod@whitby.id.au \
    --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.