[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Autoconf version number after 2.70
From: |
Bob Friesenhahn |
Subject: |
Re: Autoconf version number after 2.70 |
Date: |
Thu, 31 Dec 2020 10:21:35 -0600 (CST) |
User-agent: |
Alpine 2.20 (GSO 67 2015-01-07) |
On Thu, 31 Dec 2020, Paul Eggert wrote:
I'm more of an Autoconf user than I am an Autoconf developer, and from the
user point of view I'd rather keep things simple, and stick with 2.71 when it
comes out, and then to 2.72 when it comes out, etc.
+1 on this.
There is no reason to "ride herd" on a herd that does not exist.
Dealing with change and multiple options is hard so keep things simple
for us users. The simple approach is to keep doing what worked
fine before.
Bob
--
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
- Re: Reautoconfing, (continued)
- Re: Reautoconfing, Wookey, 2020/12/20
- Re: gnulib / autoconf sync, Bruno Haible, 2020/12/23
- Re: gnulib / autoconf sync, Bruno Haible, 2020/12/23
- Autoconf version number after 2.70, Paul Eggert, 2020/12/23
- Re: Autoconf version number after 2.70, Julien ÉLIE, 2020/12/24
- Re: Autoconf version number after 2.70, Zack Weinberg, 2020/12/30
- Re: Autoconf version number after 2.70, David A. Wheeler, 2020/12/30
- Re: Autoconf version number after 2.70, Paul Eggert, 2020/12/31
- Re: Autoconf version number after 2.70, Marko Lindqvist, 2020/12/30
- Re: Autoconf version number after 2.70, Paul Eggert, 2020/12/31
- Re: Autoconf version number after 2.70,
Bob Friesenhahn <=
Re: Request to revert the C version change, Todd C. Miller, 2020/12/16