Hi Zack, "Zack Weinberg" <[email protected]> writes:
> On Thu, Jan 15, 2026, at 6:03 PM, Paul Eggert wrote: >> On 1/14/26 04:07, Jonathan Wakely wrote: >>> Would it make sense to do an Autoconf 2.72.1 release which is >>> identical to 2.72 except it fixes this serious incompatibility with >>> GCC 16? >> >> Easier would be to simply release what we've got. > > I was thinking the same thing. We have a whole bunch of relatively low- > risk patches stacked up in git, might as well call them 2.73. > > I'd like to see some broad testing first, though. What if I put out an > alpha release sometime this week and distribution maintainers do some > mass rebuilds with it? Also, does anyone know of any high-importance > patches waiting for review, or other high-importance bugs that should be > addressed ASAP? It would be nice to get this patch of mine to avoid -Wtrailing-whitespace in config.h in [1]. You think you could apply it as my copyright assignment is pending? My email got lost in the FSF's system and once found they were running into issues with GPG signing. I decided to wait on sending a physical signature pending my acceptance to become maintainer of GNU time, to kill two birds (assignments) with one stone (mail). I sent the GNU time assignment request a day or two ago, so hopefully both will get done soon. Thanks, Collin [1] https://lists.gnu.org/archive/html/autoconf-patches/2025-10/msg00002.html
