unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com>
To: Zack Weinberg <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: glibc 2.30 - 6 days until ABI freeze.
Date: Tue, 25 Jun 2019 13:36:12 -0700	[thread overview]
Message-ID: <CAKmqyKNZicBRWu5WqZZSODbsrP739=Kp+i3bV+vMQsGQto5rhQ@mail.gmail.com> (raw)
In-Reply-To: <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

  reply	other threads:[~2019-06-25 20:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25  1:45 glibc 2.30 - 6 days until ABI freeze Carlos O'Donell
2019-06-25 17:54 ` Alistair Francis
2019-06-25 18:05   ` Zack Weinberg
2019-06-25 20:36     ` Alistair Francis [this message]
2019-06-25 23:55       ` Carlos O'Donell
2019-06-25 18:06   ` Carlos O'Donell
2019-06-25 20:57 ` Jim Wilson
2019-06-25 23:59   ` Carlos O'Donell
2019-06-26 17:52 ` Shawn Landden
2019-06-26 21:13   ` Carlos O'Donell
2019-06-27 12:33   ` Tulio Magno Quites Machado Filho
2019-06-27 16:27 ` Zack Weinberg
2019-06-27 16:53   ` Carlos O'Donell
2019-06-28  8:22 ` Dragan Mladjenovic
2019-06-28 11:22 ` Mike Crowe
2019-06-28 11:58   ` Carlos O'Donell
2019-06-28 12:10     ` Mike Crowe
2019-06-28 12:55       ` Carlos O'Donell
2019-07-04 13:39         ` Adhemerval Zanella
2019-07-04 14:30           ` Mike Crowe
2019-07-04 14:39             ` Adhemerval Zanella
2019-07-04 14:41               ` Florian Weimer
2019-07-05 15:38                 ` Mike Crowe
2019-07-09 18:04                   ` Mike Crowe
2019-07-10 20:22                     ` Adhemerval Zanella
2019-07-12  3:41                       ` Carlos O'Donell
2019-07-12 20:30                         ` Adhemerval Zanella
  -- strict thread matches above, loose matches on Subject: below --
2019-06-27  7:20 Mihailo Stojanović
2019-06-27 16:17 ` Carlos O'Donell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKmqyKNZicBRWu5WqZZSODbsrP739=Kp+i3bV+vMQsGQto5rhQ@mail.gmail.com' \
    --to=alistair23@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=zackw@panix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).