From: "naohirot@fujitsu.com" <naohirot@fujitsu.com>
To: 'Zack Weinberg' <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: RE: [PATCH 3/3] Removed obsolete AC_CHECK_TOOL_PREFIX
Date: Wed, 17 Feb 2021 01:25:20 +0000 [thread overview]
Message-ID: <TYAPR01MB6025A0B76F2F964799AC56B3DF869@TYAPR01MB6025.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAKCAbMgJGXz7mbf=5yoHZp_estRDFSyPVycwTsyG=NzYOhU2pg@mail.gmail.com>
Zack-san,
Thanks!
Naohiro
> -----Original Message-----
> From: Zack Weinberg <zackw@panix.com>
> Sent: Wednesday, February 17, 2021 1:42 AM
> To: Tamura, Naohiro/田村 直広 <naohirot@fujitsu.com>
> Cc: GNU C Library <libc-alpha@sourceware.org>
> Subject: Re: [PATCH 3/3] Removed obsolete AC_CHECK_TOOL_PREFIX
>
> On Tue, Feb 16, 2021 at 7:02 AM Naohiro Tamura <naohirot@fujitsu.com> wrote:
> > This patch removed obsolete AC_CHECK_TOOL_PREFIX.
> > It has been confirmed that AC_CHECK_TOOL_PREFIX is defined as NOP in
> > GNU 'autoconf' 2.69 [1], so we can safely remove it.
> > The 'configure' file has been deleted one blank line by the 'autoconf'
> > 2.69 command .
>
> OK, please commit.
>
> zw
next prev parent reply other threads:[~2021-02-17 1:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 12:31 [PATCH] Replaced obsoleted AC_HELP_STRING to AS_HELP_STRING Naohiro Tamura
2021-02-15 12:59 ` Adhemerval Zanella
2021-02-15 13:29 ` Mike Frysinger
2021-02-15 13:39 ` Adhemerval Zanella
2021-02-15 15:38 ` Mike Frysinger
2021-02-15 16:39 ` Adhemerval Zanella
2021-02-15 17:17 ` Florian Weimer
2021-02-15 18:51 ` Adhemerval Zanella
2021-02-15 20:21 ` Mike Frysinger
2021-02-15 20:31 ` Adhemerval Zanella
2021-02-16 2:36 ` naohirot
2021-02-16 12:01 ` [PATCH 3/3] Removed obsolete AC_CHECK_TOOL_PREFIX Naohiro Tamura
2021-02-16 16:41 ` Zack Weinberg
2021-02-17 1:25 ` naohirot [this message]
2021-02-21 23:36 ` Mike Frysinger
2021-02-22 1:48 ` naohirot
2021-02-21 21:31 ` [PATCH] Replaced obsoleted AC_HELP_STRING to AS_HELP_STRING Mike Frysinger
2021-02-22 1:41 ` naohirot
2021-02-23 2:02 ` Carlos O'Donell
2021-05-10 0:52 ` naohirot
2021-05-10 1:17 ` Mike Frysinger
2021-05-10 2:15 ` naohirot
2021-05-10 14:16 ` naohirot
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=TYAPR01MB6025A0B76F2F964799AC56B3DF869@TYAPR01MB6025.jpnprd01.prod.outlook.com \
--to=naohirot@fujitsu.com \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.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).