From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: [PATCH 11/12] etc: rename configure.in to configure.ac
Date: Tue, 9 Nov 2021 19:14:30 -0500 [thread overview]
Message-ID: <20211110001431.2212-12-vapier@gentoo.org> (raw)
In-Reply-To: <20211110001431.2212-1-vapier@gentoo.org>
The .in name has been deprecated for a long time in favor of .ac.
---
etc/{configure.in => configure.ac} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename etc/{configure.in => configure.ac} (100%)
diff --git a/etc/configure.in b/etc/configure.ac
similarity index 100%
rename from etc/configure.in
rename to etc/configure.ac
--
2.33.0
next prev parent reply other threads:[~2021-11-10 0:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 0:14 [PATCH 00/12] sync etc/ to bfd/gdb tree Mike Frysinger
2021-11-10 0:14 ` [PATCH 01/12] Fix compile time warning messages building with gcc v6.1.1 Mike Frysinger
2021-11-10 0:14 ` [PATCH 02/12] update-copyright.py for binutils Mike Frysinger
2021-11-10 0:14 ` [PATCH 03/12] Update the address of the FSF in the copyright notice of files which were using the old address Mike Frysinger
2021-11-10 0:14 ` [PATCH 04/12] Update year range in copyright notice of binutils files Mike Frysinger
2021-11-10 0:14 ` [PATCH 05/12] Bump to autoconf 2.69 and automake 1.15.1 Mike Frysinger
2021-11-10 0:14 ` [PATCH 06/12] Update year range in copyright notice of binutils files Mike Frysinger
2021-11-10 0:14 ` [PATCH 07/12] texi2pod.pl: import support for @t{...} from gcc Mike Frysinger
2021-11-10 0:14 ` [PATCH 08/12] Add libctf to update-copyright.py Mike Frysinger
2021-11-10 0:14 ` [PATCH 09/12] Update year range in copyright notice of binutils files Mike Frysinger
2021-11-10 0:14 ` [PATCH 10/12] texi2pod.pl: add no-op --no-split option support [PR28144] Mike Frysinger
2021-11-10 0:14 ` Mike Frysinger [this message]
2021-11-10 0:14 ` [PATCH 12/12] etc: switch to automake Mike Frysinger
2021-11-10 10:54 ` [PATCH 00/12] sync etc/ to bfd/gdb tree Corinna Vinschen
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=20211110001431.2212-12-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.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).