From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) by sourceware.org (Postfix) with ESMTP id A1442385800A for ; Fri, 11 Nov 2022 08:40:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A1442385800A Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gentoo.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gentoo.org Content-Type: multipart/signed; boundary="Apple-Mail=_70BF418E-38C3-4FFF-8892-46E0A691001B"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.200.110.1.12\)) Subject: Re: How can Autoconf help with the transition to stricter compilation defaults? From: Sam James In-Reply-To: <1d3109aa-c810-4c20-bcb9-d9d059d530a6@app.fastmail.com> Date: Fri, 11 Nov 2022 08:40:39 +0000 Cc: Michael Orlitzky , Autoconf Development , c-std-porting@lists.linux.dev, GCC Development Message-Id: <856910E7-DDDD-4774-B9C6-6D5941A48618@gentoo.org> References: <24ed5604-305a-4343-a1b6-a789e4723849@app.fastmail.com> <1d3109aa-c810-4c20-bcb9-d9d059d530a6@app.fastmail.com> To: Zack Weinberg X-Mailer: Apple Mail (2.3731.200.110.1.12) X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --Apple-Mail=_70BF418E-38C3-4FFF-8892-46E0A691001B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 11 Nov 2022, at 03:33, Zack Weinberg wrote: >=20 > On Thu, Nov 10, 2022, at 10:08 PM, Sam James wrote: >>> On 10 Nov 2022, at 21:10, Michael Orlitzky = wrote: >>> While everyone else is discussing big ideas, it would be helpful for = me >>> personally if autoconf just made a release with the latest bugfixes. >>=20 >> Before I dive into the rest of this thread: yes, this is one of >> my main thoughts on the matter. Autoconf has a huge network >> effect problem and letting the existing fixes start to propagate >> would be most helpful. >=20 > It would be relatively easy for me to take a couple hours this weekend = and put out a 2.72 release with everything that's already in trunk and = nothing else. Anyone have reasons I _shouldn't_ do that? > [...] >=20 > I have not been following the y2038 work closely. Is it going to = affect things in a good way or a bad way?? I've started a discussion on libc-alpha about this, but I think it = depends on how you view the migration. I've come to the conclusion it's probably good but only = after thinking about it a lot. I wish it'd been discussed on the mailing lists first, = as it's not obvious that it's okay, and I'm not sure if others will even share my view. Let's have the conversation there as it'll be easier to track. Thanks for prompting me to write this up finally. --Apple-Mail=_70BF418E-38C3-4FFF-8892-46E0A691001B Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iNUEARYKAH0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCY24Kh18UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MAAKCRBzhAn1IN+R kH1LAP93R/WcyZqbRm4uI57F8GFafFjeTGBo/8thkyHIy/BBZgEAmT8hjQfIwafv 6fEuK1DIPvrpcibMQfLcDe7pFfJKlQY= =kiOo -----END PGP SIGNATURE----- --Apple-Mail=_70BF418E-38C3-4FFF-8892-46E0A691001B--