[yocto] Upstream-Status finally @ 100%
Koen Kooi
koen at beagleboard.org
Thu Feb 9 04:22:10 PST 2012
Op 9 feb. 2012, om 00:18 heeft Saul Wold het volgende geschreven:
> On 02/08/2012 01:26 PM, Daniel Stenberg wrote:
>> On Wed, 8 Feb 2012, Saul Wold wrote:
>>
>>> If the author of curl would like to review and/or implement
>>> modification for OE that would be awesome, feel free to share the
>>> patches with them.
>>
>> I am the maintainer of curl.
>>
>> The curl patches Björn mentioned are clearly not written in way intended
>> to be "upstreamable" so they cannot be accepted by the curl project and
>> nobody has tried to.
>>
> I am sure there are many patches like that in OE, they are written, tested and then forgotten about, our goal here is to not let them get forgotten.
>
>> This said, at least one of the patches fixes a problem that still exists
>> upstream but the yocto patch [*] is made in such a hard-coded way it'd
>> have to be seriously edited to get accepted. The flaw has not even been
>> discussed with or mentioned to the curl project AFAICR...
>>
>> So, room for improvements!
>>
>> [*] =
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-support/curl/curl/noldlibpath.patch
>>
>>
>
> Daniel,
>
> I think Khem has already said that we are taking incremental steps here, as I mentioned in my prior email, we have over 1200 patches lurking around in OE currently, initially we have about 460 as marked as pending.
I find the 'pending' confusing, is it 'pending submission' or 'pending approval'? I'm marking patches in meta-oe with 'Upstream-status: Unknown' as default instead of 'Pending' to make it a bit clearer. And patches marked 'inappropriate' won't go in, it's 'rejected', 'unknown' or 'needs work' in those cases. I'm not going to guess what upstream might think of it, since I can't speak for them.
All patches in OE-core now have an Upstream-status, but how many have an *incorrect* Upstream-status? I suspect only a small percentage, but I think it's worth rethinking the lingo used to be clearer to non-native speakers like me.
regards,
Koen
More information about the yocto
mailing list