From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 82E2A1F463 for ; Fri, 20 Dec 2019 14:30:51 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type:content-transfer-encoding; q=dns; s=default; b=I+StPfKXirM8UEt8S4+n9C0CiEJzS9C1g57exwtQGJo cSE5b0nVDOpMo5m8QMSD7JaaRJIHO2Fhi/CnK1Yx0KL07sXV/0UdgErYn95r2Umq y/mPYiBJESO7SbdPl15cVSGw0kupYziV/8CvuxTrZEqzwj6dUZ5cxqgtGtGu6YnE = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type:content-transfer-encoding; s=default; bh=W9lnrd+z7vze0m+vvU8yBkEOoCY=; b=pVsLZejw5lHf0KUTs Oc+Ls0M/zOj0YXiJ/NCZVBx4vNrX44evxrZzFquXGFV68XpZdDkGU5X2+aMMK2VV RiiRR/xceVcGNI21ZvYpx4x1Ek8U726yp3ffS+dl5pPiiuh57pq6WyUyrP/9bULq Shn5hJd40bqKMLcohDQTCCxeXA= Received: (qmail 20385 invoked by alias); 20 Dec 2019 14:30:48 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 20332 invoked by uid 89); 20 Dec 2019 14:30:44 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: us-smtp-1.mimecast.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576852240; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=dGcOiTr+FkNffiOCKGk8Kpptor3OSAp+/YRPD3AJ9hg=; b=iH0JNIYiHGDFRqVpjY9x8zJ4d8VyYUCvEu18VJdrkBfA5Qc/nkD1+jVjGxq2rdiRyezDVk z7pUc6R94HOl5c72O1ulWpA3NRx9R6GtpwIdQfCfsi6bbOU6CsMUKqvk02eVvT+kVCl05K 1Sddu2NMOCHu75a5QaNfBsFzzpbqGaw= From: Florian Weimer To: Siddhesh Poyarekar Cc: GLIBC Devel Subject: Re: 2.31: < 2 weeks to go References: <0645ee7d-59c9-cb2f-ebe5-ef613c8094cf@gotplt.org> Date: Fri, 20 Dec 2019 15:30:31 +0100 In-Reply-To: <0645ee7d-59c9-cb2f-ebe5-ef613c8094cf@gotplt.org> (Siddhesh Poyarekar's message of "Fri, 20 Dec 2019 09:05:38 +0530") Message-ID: <87v9qbgjco.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable * 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. 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. Thanks, Florian