On Mon, Mar 27, 2023 at 2:49 PM Václav Haisman wrote:
> On 27. 03. 23 17:38, Jim Meyering wrote:
> > We're overdue for a new release, so here's a snapshot in preparation
> > for that, which I want to call 2.73 (skipping 2.72). There has never
> > been an autoconf-2.72 release, yet `git describe`
On Mon, Mar 27, 2023 at 10:18 AM Zack Weinberg wrote:
> On Mon, Mar 27, 2023, at 11:38 AM, Jim Meyering wrote:
> > We're overdue for a new release, so here's a snapshot in preparation
> > for that, which I want to call 2.73 (skipping 2.72). There has never
> > been an autoconf-2.72 release, yet `
On 3/27/23 10:16, Zack Weinberg wrote:
Compatibility with compilers that reject unprototyped function declarations
should maybe get a more prominent NEWS entry.
I gave that a shot by installing the attached.From 5ffc09fca39de051537fbebd7c6c33d5255a520f Mon Sep 17 00:00:00 2001
From: Paul Egger
On 3/27/23 14:49, Václav Haisman wrote:
Curious amounts of things getting wrapped in case/esac but I am assuming
that's intentional.
Yes it is:
https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=c8d6d6eb8be36144f1285f35901e325b56bac68f
On 27. 03. 23 17:38, Jim Meyering wrote:
We're overdue for a new release, so here's a snapshot in preparation
for that, which I want to call 2.73 (skipping 2.72). There has never
been an autoconf-2.72 release, yet `git describe` now prints 2.72c and
has been printing strings like v2.72a-92-g8db0
On Mon, Mar 27, 2023, at 2:30 PM, Carlos O'Donell wrote:
> On 3/27/23 13:45, Sam James wrote:
>> "Zack Weinberg" writes:
>>> On Mon, Mar 27, 2023, at 11:38 AM, Jim Meyering wrote:
We're overdue for a new release, so here's a snapshot in
preparation for that, which I want to call 2.73 (sk
On 3/27/23 13:45, Sam James wrote:
>
> "Zack Weinberg" writes:
>
>> On Mon, Mar 27, 2023, at 11:38 AM, Jim Meyering wrote:
>>> We're overdue for a new release, so here's a snapshot in
>>> preparation for that, which I want to call 2.73 (skipping 2.72).
>>> There has never been an autoconf-2.72 r
"Zack Weinberg" writes:
> On Mon, Mar 27, 2023, at 11:38 AM, Jim Meyering wrote:
>> We're overdue for a new release, so here's a snapshot in preparation
>> for that, which I want to call 2.73 (skipping 2.72). There has never
>> been an autoconf-2.72 release, yet `git describe` now prints 2.72c
On Mon, Mar 27, 2023, at 11:38 AM, Jim Meyering wrote:
> We're overdue for a new release, so here's a snapshot in preparation
> for that, which I want to call 2.73 (skipping 2.72). There has never
> been an autoconf-2.72 release, yet `git describe` now prints 2.72c and
> has been printing strings
We're overdue for a new release, so here's a snapshot in preparation
for that, which I want to call 2.73 (skipping 2.72). There has never
been an autoconf-2.72 release, yet `git describe` now prints 2.72c and
has been printing strings like v2.72a-92-g8db00aa8 for years.
If you maintain a package
10 matches
Mail list logo
