On 01.11.2019. 12:49, Adhemerval Zanella wrote:
>
>
> On 01/11/2019 06:02, Dragan Mladjenovic wrote:
>> On 31.10.2019. 18:18, Florian Weimer wrote:
>>> * Dragan Mladjenovic:
>>>
>>>> Sorry for this really late response. I finally managed to get my test
>>>> machines in order. If it helps, I rechecked old releases and patched
>>>> ones on 5.3 kernel /-hard-float/-EB/-mabi=o32/n32/n64 w/ and w/o
>>>> exec-stack by default and there were no new failures. What do I do next?
>>>> Do I need to get the approval of release manager for each branch
>>>> individually?
>>>
>>> No, if it fixes a bug and does not add symbols, you can backport it on
>>> your own and commit it.  We expect some diligence regarding testing, but
>>> we have no way of enforcing that.
>>>
>>> Thanks,
>>> Florian
>>>
>>
>> But I don't have write access to the glibc repo. I would be grateful if
>> someone who can do it for me. I can provide patches that apply to each
>> branch without change if it helps to ease the friction of backporting.
>>
>> Thanks in advance,
>> Dragan
>>
>
> Alright, just point me to a repo and I can sort this out for you.
>

Thanks,

I'm targeting release/2.24/master...release/2.30/master branches.
I don't have a publicly visible repo with the patches.
If it helps, there are patches for each of the branches in the attachment.

Best regards,
Dragan