linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [e2fsprogs] rename configure.in to configure.ac
Date: Mon, 8 Jun 2015 11:56:06 -0400	[thread overview]
Message-ID: <20150608155606.GD13517@vapier> (raw)
In-Reply-To: <20150608145922.GA15795@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]

On 08 Jun 2015 10:59, Theodore Ts'o wrote:
> On Mon, May 25, 2015 at 05:32:32AM -0400, Mike Frysinger wrote:
> > Newer versions of autotools have started warning when using the old
> > configure.in name.
> 
> Note that I ship a version of configure (and keep one checked in to
> git) because I do not trust the autoconf maintainers' ability to
> maintain backwards compatibility, having gotten badly burned in the
> past.  I am currently using autoconf 2.69, and people who try to rerun
> autoconf on some other version of autoconf are venturing into
> unsupported territory.  It may work; it may screw up in amazing ways.
> Some autoconf macro may silently assume that some feature is present
> when it is not, or vice versa.
> 
> And if it breaks, you get to keep both pieces.  :-)

that's fine, but it doesn't really matter to this patch -- it should be 
configure.ac and not configure.in.  the version of autoconf you're using 
certainly supports the newer name.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-06-08 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25  9:32 [PATCH e2fsprogs] rename configure.in to configure.ac Mike Frysinger
2015-06-08 14:59 ` [e2fsprogs] " Theodore Ts'o
2015-06-08 15:56   ` Mike Frysinger [this message]
2015-06-20 19:21     ` Theodore Ts'o

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=20150608155606.GD13517@vapier \
    --to=vapier@gentoo.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).