Re: glibc 2.29 - Winter is coming...

[Ramana Radhakrishnan <ramana dot gcc at googlemail dot com>]

On Tue, Jan 8, 2019 at 4:50 PM Carlos O'Donell <carlos@redhat.com> wrote:
>
> On 1/8/19 9:21 AM, Szabolcs Nagy wrote:
> > 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.
>
> Sorry, my intent was only to specify that there is a blocker on
> these patches. I am working with Feng Xue directly such that once
> the copyright status is confirmed, I can move forward with account
> setup so AmpereComputing can commit their own approved patches.

I saw the copyright assignment go past on the GCC side when it
happened and see this in copyright.list on fencepost ..

GCC GLIBC       Ampere Computing LLC    2018-12-05
Assigns Past and Future Changes
Mauri Whalen (Vice President Software Engineering)

regards
Ramana


>
> --
> Cheers,
> Carlos.