[oe] [STABLE][PATCH v2] mingw-binutils: update to 2.19.1

[Esben Haabendal]

On Wed, Apr 8, 2009 at 7:50 PM, Tom Rini <trini at kernel.crashing.org> wrote:
> On Wed, Apr 08, 2009 at 01:38:39PM -0400, Philip Balister wrote:
>> Esben Haabendal wrote:
>>> On Wed, Apr 8, 2009 at 4:26 PM, Koen Kooi <k.kooi at student.utwente.nl> wrote:
>>>> On 08-04-09 16:16, Esben Haabendal wrote:
>>>>
>>>>> Then, please someone apply this to .dev.  But then how are we supposed
>>>>> to remember which patches should also be moved to stable, and when?
>>>> If you want something in stable, you send the patch to this mailinglist with
>>>> [STABLE] in the subject.
>>>
>>> Which is exactly what I did.  Now 3 times even.
>>
>> I suspect the problem is most of the people interested in stable do not
>> know what this patch does. I admit to skimming over things that look
>> like patches to pieces of OE that I know little about.
>>
>> Still, we need a way to get this sort of thing into stable, even when it
>> is outside the scope of most of the reviewers.
>
> Hang on.  I (the guy signed up to own this part of stable) have reviewed
> it each time.  The problem is there's been both general little problems
> and Esben has wanted the patch to go in both trees at once, which isn't
> how I understand Stable to work.
>
> My plan right now is to fixup the still minor problems in v3 and post
> for stable momentarily.

That is fine.  And it is also good that we improve the quality of the
metadata when changing stuff.
But it is just surprising that when I copy an existing recipe file to
add a new version, it gives rise to so much need for improvement.
The existing file were committed by yourself, although it originates
from my canadian sdk work, but I maybe we could use time a bit more
efficient than nitpicking to much on selected commit(ter)s. That said,
it is always nice to have the best possible end result :-)

/Esben