From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH 1/2] newlib: drop unused cache vars from Makefiles
Date: Thu, 3 Feb 2022 13:08:30 +0100 [thread overview]
Message-ID: <YfvFvhkn9mL6eNJO@calimero.vinschen.de> (raw)
In-Reply-To: <20220202025256.32179-1-vapier@gentoo.org>
On Feb 1 21:52, Mike Frysinger wrote:
> These aren't used in any of the makefiles, so there's no point in
> exporting these. These are only checked in the configure script.
> ---
> newlib/Makefile.in | 2 --
> newlib/configure | 8 ++------
> newlib/configure.ac | 2 --
> 3 files changed, 2 insertions(+), 10 deletions(-)
Cover letter? Pleeeeeease?
Patchset is ok to push.
Thanks,
Corinna
prev parent reply other threads:[~2022-02-03 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 9:44 newlib_cv_ vs libc_cv_ autoconf cache vars prefix Mike Frysinger
2022-01-31 14:17 ` Corinna Vinschen
2022-02-01 3:12 ` Mike Frysinger
2022-02-01 14:55 ` Corinna Vinschen
2022-02-02 2:52 ` [PATCH 1/2] newlib: drop unused cache vars from Makefiles Mike Frysinger
2022-02-02 2:52 ` [PATCH 2/2] newlib: rename libc_cv_ prefix to newlib_cv_ Mike Frysinger
2022-02-03 12:08 ` Corinna Vinschen [this message]
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=YfvFvhkn9mL6eNJO@calimero.vinschen.de \
--to=vinschen@redhat.com \
--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).