public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH 0/5] newlib: phoenix: kill off all subdir configure scripts
Date: Tue, 15 Feb 2022 14:38:01 +0100	[thread overview]
Message-ID: <YgusuUdC2hI3cDrp@calimero.vinschen.de> (raw)
In-Reply-To: <20220210085126.21023-1-vapier@gentoo.org>

On Feb 10 03:51, Mike Frysinger wrote:
> With sys/linux/ gone, this is the only tree left with configure scripts
> below libc/, so spend some time cleaning these up specially.  This gets
> us down to 2 configure scripts in all of newlib.
> 
> Mike Frysinger (5):
>   newlib: phoenix: move some logic from configure to the Makefile
>   newlib: phoenix: drop missing machine subdirs
>   newlib: phoenix: merge machine/ trampoline up a level
>   newlib: phoenix: merge machine/ configure scripts up a level
>   newlib: phoenix: merge configure up to top-level

Thanks, please push.


Corinna


      parent reply	other threads:[~2022-02-15 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  8:51 Mike Frysinger
2022-02-10  8:51 ` [PATCH 1/5] newlib: phoenix: move some logic from configure to the Makefile Mike Frysinger
2022-02-10  8:51 ` [PATCH 2/5] newlib: phoenix: drop missing machine subdirs Mike Frysinger
2022-02-10  8:51 ` [PATCH 3/5] newlib: phoenix: merge machine/ trampoline up a level Mike Frysinger
2022-02-10  8:51 ` [PATCH 4/5] newlib: phoenix: merge machine/ configure scripts " Mike Frysinger
2022-02-10  8:51 ` [PATCH 5/5] newlib: phoenix: merge configure up to top-level Mike Frysinger
2022-02-15 13:38 ` 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=YgusuUdC2hI3cDrp@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).