From: Sam James <sam@gentoo.org>
To: Jim Meyering <jim@meyering.net>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
Frederic Berat <fberat@redhat.com>,
Zack Weinberg <zack@owlfolio.org>,
Florian Weimer <fweimer@redhat.com>, Wookey <wookey@wookware.org>,
autoconf-patches@gnu.org, c-std-porting@lists.linux.dev
Subject: Re: time for Autoconf 2.72 (was: On time64 and Large File Support)
Date: Sun, 19 Mar 2023 00:57:52 +0000 [thread overview]
Message-ID: <87mt49y2t7.fsf@gentoo.org> (raw)
In-Reply-To: <CA+8g5KF1AquJQB9ZhQv=+jau7Ud5_8N45q9jcLvGj3eyGfN0-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
Jim Meyering <jim@meyering.net> writes:
> On Fri, Mar 17, 2023 at 7:52 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
>> On 3/17/23 19:08, Jim Meyering wrote:
>> > Can someone see if there's some small/safe set of changes that are essential?
>> > If none (or few/easy), I might have time to make a snapshot soon.
>>
>> As far as I know, none of the pending patches are essential and we can
>> release what we have.
>
> Good. Thanks. It just so happens that I'm about to make a snapshot of
> grep (for this:
> https://lists.gnu.org/r/bug-grep/2023-03/msg00005.html) using the very
> latest autoconf, including many changes that were not used in making
> grep-3.9 (I was surprised to realize 3.9 was bootstrapped with
> something near v2.72a-65-gd081ac3e, from October(!)). Let's see how
> grep snapshot testing goes, and if there's no objection by then, I'll
> plan to make an autoconf snapshot within a week or so.
Thanks Jim. Please give me a shout if I can assist. And I'll go test
the new grep snap.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next prev parent reply other threads:[~2023-03-19 0:58 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 8:38 On time64 and Large File Support Sam James
2022-11-11 9:16 ` Paul Eggert
2022-11-11 9:19 ` Sam James
2022-11-11 23:48 ` Joseph Myers
2022-11-11 9:19 ` Florian Weimer
2022-11-11 9:27 ` Sam James
2022-11-11 11:38 ` Florian Weimer
2022-11-11 20:12 ` Paul Eggert
2022-11-12 2:20 ` Zack Weinberg
2022-11-12 3:57 ` Sam James
2022-11-12 14:16 ` Zack Weinberg
2022-11-12 17:41 ` Paul Eggert
2022-11-12 18:50 ` Bruno Haible
2022-11-12 19:15 ` Paul Eggert
2022-11-12 20:23 ` Wookey
2022-11-12 20:54 ` Russ Allbery
2022-11-12 21:31 ` Paul Eggert
[not found] ` <951fc967-042c-4978-bd78-8bc4c8706b18@app.fastmail.com>
2022-11-13 5:11 ` Zack Weinberg
2022-11-15 5:06 ` Sam James
2022-12-25 19:19 ` Paul Eggert
2022-12-29 4:02 ` Zack Weinberg
2022-12-30 22:12 ` Paul Eggert
2022-12-30 22:20 ` Sam James
2023-01-20 9:56 ` Paul Eggert
2023-02-02 6:43 ` Sam James
2023-02-02 23:15 ` time for Autoconf 2.72 (was: On time64 and Large File Support) Paul Eggert
2023-02-02 23:17 ` Zack Weinberg
2023-02-03 5:49 ` Sam James
2023-02-03 12:43 ` time for Autoconf 2.72 Bruno Haible
[not found] ` <CAObJKZp2CCRR46-X9NYaRES7eDCVyoJ0xv=u4aSG2KeQv4vtjA@mail.gmail.com>
2023-02-27 2:30 ` time for Autoconf 2.72 (was: On time64 and Large File Support) Sam James
2023-03-17 23:47 ` Sam James
2023-03-18 0:59 ` Paul Eggert
2023-03-18 2:08 ` Jim Meyering
2023-03-18 2:52 ` Paul Eggert
2023-03-19 0:30 ` Jim Meyering
2023-03-19 0:57 ` Sam James [this message]
2022-11-15 5:09 ` On time64 and Large File Support Sam James
2022-11-12 18:19 ` Paul Eggert
2022-11-11 9:40 ` Andreas K. Huettel
2022-11-11 11:30 ` Florian Weimer
2022-11-11 19:01 ` Andreas K. Huettel
2022-11-11 19:28 ` Palmer Dabbelt
2022-11-11 9:46 ` Paul Eggert
2022-11-11 11:22 ` Florian Weimer
2022-11-11 19:56 ` Paul Eggert
2022-11-12 4:20 ` Wookey
2022-11-12 4:28 ` Sam James
2022-11-12 4:56 ` Wookey
2022-11-12 4:59 ` Sam James
2022-11-12 18:33 ` Paul Eggert
2022-11-14 8:39 ` Adam Sampson
2022-11-14 11:47 ` Florian Weimer
2022-11-14 20:26 ` Arsen Arsenović
2022-11-14 20:52 ` Florian Weimer
2022-11-15 7:39 ` Arsen Arsenović
2022-11-11 10:25 ` Richard Purdie
2023-03-01 22:38 ` Eric Blake
2023-03-02 0:29 ` Demi Marie Obenour
2023-03-02 9:04 ` Daniel P. Berrangé
2023-03-02 10:28 ` Paul Eggert
2023-03-02 10:38 ` Andreas Schwab
2023-03-03 5:46 ` Paul Eggert
2023-03-06 8:58 ` Andreas Schwab
2023-03-06 10:19 ` Florian Weimer
2023-03-02 11:02 ` Richard W.M. Jones
2023-03-02 12:17 ` Bruno Haible
2023-03-02 13:24 ` Daniel P. Berrangé
2023-03-03 3:30 ` Wookey
2023-03-03 5:50 ` Paul Eggert
2023-03-03 14:01 ` Wookey
2023-03-03 14:14 ` Daniel P. Berrangé
2023-03-03 23:21 ` Arsen Arsenović
2023-03-03 11:49 ` Florian Weimer
2023-03-03 12:39 ` Richard W.M. Jones
2023-03-02 8:30 ` Richard W.M. Jones
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=87mt49y2t7.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=autoconf-patches@gnu.org \
--cc=c-std-porting@lists.linux.dev \
--cc=eggert@cs.ucla.edu \
--cc=fberat@redhat.com \
--cc=fweimer@redhat.com \
--cc=jim@meyering.net \
--cc=wookey@wookware.org \
--cc=zack@owlfolio.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