From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH 0/8] libgloss: more merging of configure scripts
Date: Wed, 16 Feb 2022 09:40:02 +0100 [thread overview]
Message-ID: <Ygy4YpomKyn9YTGp@calimero.vinschen.de> (raw)
In-Reply-To: <20220211125054.12397-1-vapier@gentoo.org>
On Feb 11 07:50, Mike Frysinger wrote:
> More work to reduce the number of configure scripts in libgloss.
> Fairly mechanical at this point. Gets us down to 8 total.
>
> Mike Frysinger (8):
> libgloss: i386: simplify target flags
> libgloss: merge i386 configure script up a level
> libgloss: merge moxie configure script up a level
> libgloss: merge mcore configure script up a level
> libgloss: m68k: switch to AC_NO_EXECUTABLES
> libgloss: merge m68k configure script up a level
> libgloss: merge mn10200 configure script up a level
> libgloss: merge mn10300 configure script up a level
Small typo in commit message 1/8 (eaiser -> easier)
LGTM, please push.
Thanks,
Corinna
prev parent reply other threads:[~2022-02-16 8:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 12:50 Mike Frysinger
2022-02-11 12:50 ` [PATCH 1/8] libgloss: i386: simplify target flags Mike Frysinger
2022-02-11 12:50 ` [PATCH 2/8] libgloss: merge i386 configure script up a level Mike Frysinger
2022-02-11 12:50 ` [PATCH 3/8] libgloss: merge moxie " Mike Frysinger
2022-02-11 12:50 ` [PATCH 4/8] libgloss: merge mcore " Mike Frysinger
2022-02-11 12:50 ` [PATCH 5/8] libgloss: m68k: switch to AC_NO_EXECUTABLES Mike Frysinger
2022-02-11 12:50 ` [PATCH 6/8] libgloss: merge m68k configure script up a level Mike Frysinger
2022-02-11 12:50 ` [PATCH 7/8] libgloss: merge mn10200 " Mike Frysinger
2022-02-11 12:50 ` [PATCH 8/8] libgloss: merge mn10300 " Mike Frysinger
2022-02-12 10:20 ` [PATCH] libgloss: merge mips " Mike Frysinger
2022-02-16 8:40 ` 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=Ygy4YpomKyn9YTGp@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).