From: "Carlos O'Donell" <carlos@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: libc-alpha@sourceware.org, libc-ports@sourceware.org
Subject: Re: [PATCH] rename configure.in to configure.ac
Date: Fri, 06 Sep 2013 05:28:00 -0000 [thread overview]
Message-ID: <522967E6.6030801@redhat.com> (raw)
In-Reply-To: <1378339628-28867-1-git-send-email-vapier@gentoo.org>
On 09/04/2013 08:07 PM, Mike Frysinger wrote:
> Autoconf has been deprecating configure.in for quite a long time.
> Rename all our configure.in and preconfigure.in files to .ac.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
OK by me if you also update the wiki page on regeneration of files:
https://sourceware.org/glibc/wiki/Regeneration
I'm assuming you tested with old and new autoconf within the
allowances of our recommended minimum versions and it worked fine.
Cheers,
Carlos.
next prev parent reply other threads:[~2013-09-06 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 0:07 Mike Frysinger
2013-09-06 5:28 ` Carlos O'Donell [this message]
2013-09-06 6:53 ` Russ Allbery
2013-10-16 3:31 ` Allan McRae
2013-10-26 6:24 ` Allan McRae
2013-10-28 23:07 ` Roland McGrath
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=522967E6.6030801@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).