From: "Jan Beulich" <JBeulich@suse.com>
To: "Michael Darling" <darlingm@gmail.com>
Cc: "GCC Patches" <gcc-patches@gcc.gnu.org>,
"H.J. Lu" <hjl.tools@gmail.com>,"Binutils"
<binutils@sourceware.org>, "GDB" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [4/14] Completes renaming of configure.in files to .ac
Date: Fri, 17 Jul 2015 06:43:00 -0000 [thread overview]
Message-ID: <55A8C01802000078000924CF@mail.emea.novell.com> (raw)
In-Reply-To: <CABRuA+gtfPqbs5WbBa8YVRB-uga1uU2b70yat45Xyzh36owLgA@mail.gmail.com>
>>> On 17.07.15 at 06:26, <darlingm@gmail.com> wrote:
> Which imported packages use configure.in? I'm happy to submit patches
> for those, too.
The answer to this may not even matter - consuming components
(like gcc is in respect to binutils) shouldn't assume only the newer
name is used: It should remain to be possible to build with older
versions. I.e. you always have to check for both .ac and .in when
looking for a file.
Jan
next prev parent reply other threads:[~2015-07-17 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 3:10 Michael Darling
2015-07-17 3:38 ` H.J. Lu
2015-07-17 4:26 ` Michael Darling
2015-07-17 6:43 ` Jan Beulich [this message]
2015-07-17 8:38 ` Michael Darling
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=55A8C01802000078000924CF@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=darlingm@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
/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).