unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: GLIBC Devel <libc-alpha@sourceware.org>,
	Joseph Myers <joseph@codesourcery.com>
Subject: Re: 2.31: < 2 weeks to go
Date: Sun, 22 Dec 2019 23:08:36 +0530	[thread overview]
Message-ID: <f941ade4-8e30-4819-b3a8-43d904b4b313@gotplt.org> (raw)
In-Reply-To: <87v9qbgjco.fsf@oldenburg2.str.redhat.com>

On 20/12/19 8:00 pm, Florian Weimer wrote:
> * Siddhesh Poyarekar:
> 
>> Less than two weeks to go for 2.31 freeze.  I intend to announce a
>> freeze on 31st December around afternoon IST.  Here's a reminder that if
>> you'd like your patchset considered for inclusion during the freeze, it
>> needs to be in the blockers list on the release page[1].  Please cc me
>> in patch pings if you haven't been able to get reviews and need attention.
> 
> What should we do about the built-in system call tables?  I think it's
> desirable to have this in the release to get a well-defined system call
> profile after the the Y2038 changes.  Otherwise, there will be a lot of
> variance regarding the system calls glibc makes depending on which
> version of the kernel headers glibc was built with.
> 
>   <https://sourceware.org/ml/libc-alpha/2019-12/msg00567.html>
> 
> The actual code changes (the first two patches) could go in before the
> build-many-glibcs.py changes have been reviewed.  I think the updating
> logic now follows Joseph's suggestion, but I don't know if the changes I
> did on build-many-glibcs.py are acceptable from a consistency/style
> perspective.

I took a quick look at the patches and the discussions earlier and it
looked to me like they're headed in the right direction.  Joseph, do you
agree?  If you don't have the bandwidth to do a full review, I can help
with that.

Siddhesh

  reply	other threads:[~2019-12-22 17:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20  3:35 2.31: < 2 weeks to go Siddhesh Poyarekar
2019-12-20  3:56 ` Carlos O'Donell
2019-12-20  9:45   ` Arjun Shankar
2019-12-24 14:36   ` Chung-Lin Tang
2019-12-27 12:39     ` Carlos O'Donell
2020-01-07 19:29     ` Carlos O'Donell
2019-12-20 14:30 ` Florian Weimer
2019-12-22 17:38   ` Siddhesh Poyarekar [this message]
2019-12-22 18:59     ` Joseph Myers
2019-12-30 12:20 ` Siddhesh Poyarekar
2019-12-30 15:00   ` Florian Weimer

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=f941ade4-8e30-4819-b3a8-43d904b4b313@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    /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).