All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] angstrom-2010.x.conf: Prefer binutils 2.21 and	uclibc-git
Date: Mon, 24 Jan 2011 07:52:37 -0700	[thread overview]
Message-ID: <4D3D9235.109@mentor.com> (raw)
In-Reply-To: <AANLkTikqMQ8_xZZUjrm3Cu2GVJ5COM0u5PFuGAvyst+2@mail.gmail.com>

On 01/24/2011 02:59 AM, Frans Meulenbroeks wrote:
> 2011/1/24 Koen Kooi<k.kooi@student.utwente.nl>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 24-01-11 10:15, Khem Raj wrote:
>>> On Mon, Jan 24, 2011 at 1:02 AM, Koen Kooi<k.kooi@student.utwente.nl>  wrote:
>>> On 24-01-11 03:03, Khem Raj wrote:
>>>>>> * no need to pin older udev with uclibc/git either
>>>>>>
>>>>>> Signed-off-by: Khem Raj<raj.khem@gmail.com>
>>>
>>> NAK! binutils 2.21 introduces way too many problem at this moment, those
>>> need to get solved before switching to it.
>>>
>>>> hmmm. Too vague a statement. Do you have list of issues somewhere I can look at
>>>> it built the console-image x11-image images I tried and booted
>>>> console-image too.
>>
>> Try building anything that uses linux-omap-psp 2.6.32. You will run into
>> the secure mode problem. That one is relatively easy to solve, but it
>> needs to get solved *before* the switch, not after.
>>
>> But besided that, so a change needs to get RFC'd, tested and signed off
>> by the angstrom maintainers before it gets pushed. It's a toolchain
>> change and we take toolchains seriously.
>>
>> Waking up and seeing it applied without all that is *extremely*
>> insulting. So I reverted it.
>>
>
> Pushing distro changes without review is against the policy:
>
>> From http://www.openembedded.org/index.php/Commit_Policy:
>
>   * Distro config changes should be reviewed by the distro maintainers
>     where known
>
> Reveting changes from others is also against the policy:
>
> http://www.openembedded.org/index.php/Revert_Policy
>
> (and imho equally bad (or insulting if you prefer))
>
>
> Do unto others as you would have them do unto you

Well, no.  I'm pretty sure the "you just broke my distribution" falls 
into the yes, it's OK to push the revert before the other party wakes up 
and says "Oops, sorry!".

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-01-24 14:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24  2:03 [PATCH] angstrom-2010.x.conf: Prefer binutils 2.21 and uclibc-git Khem Raj
2011-01-24  9:02 ` Koen Kooi
2011-01-24  9:15   ` Khem Raj
2011-01-24  9:39     ` Koen Kooi
2011-01-24  9:59       ` Frans Meulenbroeks
2011-01-24 14:52         ` Tom Rini [this message]
2011-01-24 15:15         ` Philip Balister
2011-01-24 15:28           ` Tom Rini
2011-01-24 15:42             ` Khem Raj
2011-01-24 15:38       ` Khem Raj
2011-01-24 16:08         ` Andreas Oberritter

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=4D3D9235.109@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.