This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: glibc 2.29 - Winter is coming...


On 08/01/2019 14:16, Carlos O'Donell wrote:
> On 1/8/19 8:33 AM, Szabolcs Nagy wrote:
>> On 02/01/2019 10:28, Siddhesh Poyarekar wrote:
>>> Status of Release blockers:
>>>
>>> I have reviewed all original release blockers, including a couple of additional ones that got added later but I couldn't get to all of them. As
>>> of now, the pending blockers do not look suitable for inclusion at this stage and so will be deferred to 2.30 development.
>>
>> i'd like to commit some patches that only affect aarch64
>> (and only particular uarches there):
>>
>> memchr and memset for AmpereComputing emag (approved before freeze):
>> https://sourceware.org/ml/libc-alpha/2018-12/msg00626.html
>> https://sourceware.org/ml/libc-alpha/2018-12/msg00628.html
>> https://sourceware.org/ml/libc-alpha/2018-12/msg00820.html
> 
> AmpereComputing is not yet listed in the FSF copyright files,
> and I don't have confirmation from the FSF (it has been asked).

ah, my bad then.

> 
>> ifunc for ares (does not add new implementation):
>> https://sourceware.org/ml/libc-alpha/2018-12/msg00754.html

this one still stands, i assume it's ok for me to commit it.

>>
>> these seem safer to me to commit now than to backport them
>> later and should not interfere with the glibc release process. 
> 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]