From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: libc-alpha@sourceware.org
Cc: "Andreas K. Huettel" <dilfridge@gentoo.org>
Subject: autoconf 2.72 ? (Re: Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release)
Date: Tue, 02 Jan 2024 10:21:46 +0100 [thread overview]
Message-ID: <2945535.X9hSmTKtgW@noumea> (raw)
In-Reply-To: <2652861.NG923GbCHz@noumea>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
Am Montag, 1. Januar 2024, 14:18:01 CET schrieb Andreas K. Huettel:
>
> What else should we add here that still needs to go into 2.39?
>
Given that it contains the fixes for recent C compilers, would updating
to autoconf 2.72 (released in november) make sense?
I admit this is rather fresh, but otoh some advance planning makes sense here.
I can regenerate and prepare a patch, but would definitely appreciate more eyes
on it then.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, comrel, toolchain, base-system, perl, libreoffice)
https://wiki.gentoo.org/wiki/User:Dilfridge
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-02 9:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 13:18 Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release Andreas K. Huettel
2024-01-02 9:14 ` Florian Weimer
2024-01-02 9:21 ` Andreas K. Huettel [this message]
2024-01-02 10:27 ` autoconf 2.72 ? (Re: Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release) Florian Weimer
2024-01-02 17:35 ` Paul Eggert
2024-01-02 19:17 ` [PATCH, test conversion, RFC] Convert to autoconf 2.72 (no patches) Andreas K. Hüttel
2024-01-02 21:30 ` Florian Weimer
2024-01-03 4:13 ` Paul Eggert
2024-01-10 18:37 ` Carlos O'Donell
2024-01-02 14:39 ` Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release Adhemerval Zanella Netto
2024-01-06 12:27 ` Andreas K. Huettel
2024-01-08 12:54 ` Adhemerval Zanella Netto
2024-01-02 15:22 ` H.J. Lu
2024-01-06 22:29 ` Andreas K. Huettel
2024-01-03 21:57 ` enh
2024-01-10 18:38 ` Carlos O'Donell
2024-01-10 20:33 ` Jeff Law
2024-01-11 1:10 ` Palmer Dabbelt
2024-01-12 6:13 ` Palmer Dabbelt
2024-01-11 22:24 ` Freeze for the upcoming glibc 2.39 release - status Andreas K. Huettel
2024-01-12 10:56 ` Adhemerval Zanella Netto
2024-01-12 13:14 ` Xi Ruoyao
2024-01-12 13:25 ` Andreas K. Huettel
2024-01-12 14:23 ` Andreas K. Huettel
2024-01-12 17:19 ` Carlos O'Donell
2024-01-12 17:34 ` Palmer Dabbelt
2024-01-12 18:10 ` Adhemerval Zanella Netto
2024-01-12 22:10 ` Palmer Dabbelt
2024-01-12 22:21 ` Freeze for the upcoming glibc 2.39 release - status (2) Andreas K. Huettel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2945535.X9hSmTKtgW@noumea \
--to=dilfridge@gentoo.org \
--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).