> On 20 Jan 2023, at 09:56, Paul Eggert <egg...@cs.ucla.edu> wrote: > > On 2022-12-30 14:12, Paul Eggert wrote: >> I'm attaching a proposed patch to Autoconf master documentation in two forms. > Zack, any further thoughts on that Autoconf patch? If not, I'm inclined to > install it as it doesn't change behavior, only documentation, and Sam wrote > that he was happy with the patch. For convenience I'm reattaching the same > patch to this email. > > Also, is there anything else blocking a new Autoconf > release?<0001-Improve-year-2038-documentation.patch>
FWIW, Clang 16 branched a week ago. Unfortunately, I think we've missed the Debian freeze I think, but it is what it is there (was hoping to get it in there so we could benefit from the large number of people who make dist tarballs on Debian). Unfortunately, the current issues from autoconf continue to pose a lot of noise for me during the C porting work. Regenerating from master cleans things up a tonne though.
signature.asc
Description: Message signed with OpenPGP
