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=-3.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,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 61A301F461 for ; Thu, 27 Jun 2019 16:53:12 +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:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=WxIpG1/PD6D5sppq b4iymvKPeZNGVHbbYuAZhlnCBcY5uCE7+HA1TkbWoaie6a6cmjmLICfSHbRfaVXw 0ewenBxkpx9WRL8x9p6voJv4hv4eAU4YG9o/gFY1u9SbgFJ7ZMLIivc22E9Yj7rd OVbB+6k0j6A9u9CGAzRcNXPvUOg= 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:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=uw+1wL2TX6YpRKq6vcztFI n9yYs=; b=wCxHm9dpL3f4novB6cui3+18e2Cp6Gw+glT37OMMxWSjRH8OOidom9 YwinO/Ks3ebMrykiHUz2HwHn4Y0C1ZkxWHTbgyFcygA/gH9fnnrJXB5GVMmOPh6H UtWQfCPAOJNqwxM9XnvASAEjF6ybJtjhXgZEkFhO4zWFWo7wPk7Ag= Received: (qmail 130374 invoked by alias); 27 Jun 2019 16:53:10 -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 130021 invoked by uid 89); 27 Jun 2019 16:53:10 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mail-qt1-f194.google.com Subject: Re: glibc 2.30 - 6 days until ABI freeze. To: Zack Weinberg Cc: GNU C Library References: From: Carlos O'Donell Message-ID: Date: Thu, 27 Jun 2019 12:53:04 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 6/27/19 12:27 PM, Zack Weinberg wrote: > On Mon, Jun 24, 2019 at 9:45 PM Carlos O'Donell wrote: >> >> If you have posted a patch that changes or adds a new >> ABI *cough* RISC-V 32-bit *cough* then please consider >> adding yourself to the "Rlease blockers?" list on the >> release page: >> >> https://sourceware.org/glibc/wiki/Release/2.30#Release_blockers.3F >> >> Anyone else with changes should do so also. > > Can I get a quick opinion from you as to whether my "public header > file hygiene improvements" patchset > (https://sourceware.org/ml/libc-alpha/2019-06/msg00773.html) is 2.30 > material at this point or whether it should wait for 2.31? My quick opinion is that this is going to break a bunch of stuff and that's OK, we'll fix the fallout. However, that to me means that we should commit it when 2.31 opens, and *right away* to get 6 months of downstream tumbleweed/rawhide testing with the changes. -- Cheers, Carlos.