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

Philip Balister philip at balister.org
Wed Apr 8 17:38:39 UTC 2009


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.

The good news is the queue of stuff to go into stable is not growing out 
of control, but we need to work out a solution to deal with "orphaned" 
patches.

Philip


> 
>> That way it will show up here:
>>
>> http://patchwork.openembedded.org/project/openembedded/list/?state=*&q=oe%2CSTABLE
>>
>> or for a complete historic view:
>>
>> http://patchwork.openembedded.org/project/openembedded/list/?q=oe,STABLE&archive=both&state=*
>>
>>> Let's not make it to complicated to maintain stable, so that it will die
>>> from us again :-(
>> Stuff needs to get into .dev first to receive wider testing. Putting stuff
>> directly in stable negates the idea of the stable branch.
> 
> Naturally, but (2 but's):
> 
> 1. When .dev is sufficiently different from stable, some fixes needed
> for stable will not make sense or work on .dev, so this rule will have
> to be bent once in a while, and most likely, more often when
> stable/2009 gets old.
> 
> 2. There must be a some sensible elastic, as straight out simple fixes
> IMHO, could just go in both at the same time.  But I guess, my opinion
> on this matter does not really matter.
> 
> It is quite impressive how difficult it can be made to submit what is
> mainly just a copy action of a file...
> 
> /Esben
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3303 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20090408/d4546bfc/attachment-0002.bin>


More information about the Openembedded-devel mailing list