This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.30 - 6 days until ABI freeze.
- From: Alistair Francis <alistair23 at gmail dot com>
- To: Zack Weinberg <zackw at panix dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 25 Jun 2019 13:36:12 -0700
- Subject: Re: glibc 2.30 - 6 days until ABI freeze.
- References: <c844bfaf-e459-1b6c-3bf2-81adb1ea3a0b@redhat.com> <CAKmqyKOgY2uSX5hf=GSiVDQV3A_B4c-rzvcvV8wY9haoZYJy+w@mail.gmail.com> <CAKCAbMgv7yHTh+zz3Mg9FpwNX3rYPGSUtH=ttMyxf=mb6i0waQ@mail.gmail.com>
On Tue, Jun 25, 2019 at 11:05 AM Zack Weinberg <zackw@panix.com> wrote:
>
> On Tue, Jun 25, 2019 at 1:57 PM Alistair Francis <alistair23@gmail.com> wrote:
> > I have been pushing to get the RV32 port into glibc 2.30, but with 6
> > days left I'm not sure it can be done.
> ...
> > In saying that I would still like the patches "finalised" soon so we
> > can at least have a fork for testing and then have this merged as soon
> > as the 2.31 window opens.
>
> I don't know if "finalised" is realistic in the time available either;
> you're tripping over some pretty deep problems and tangled up with the
> 64-bit time_t changes. There are only a few people qualified to
> review your patches, and it's going to take time and thought.
Even more reason to skip the 2.30 release.
>
> However, if you already have commit privileges (do you?) you are
> welcome to create a public testing branch right now, named <your
> sourceware userid>/rv32 or something like that. It can be
> force-pushed as necessary.
I don't have commit privileges, for the time being I'm just using my
own git repo. How do I get commit privileges?
Alistair
>
> zw