From: Mike Frysinger <vapier@gentoo.org>
To: C Howland <cc1964t@gmail.com>
Cc: newlib@sourceware.org
Subject: Re: [PATCH 1/8] newlib: internalize HAVE_INITFINI_ARRAY
Date: Wed, 19 Jan 2022 18:50:19 -0500 [thread overview]
Message-ID: <Yeiju1luBDTBJwu5@vapier> (raw)
In-Reply-To: <CANk6obSyBPsc5fR88tkvCsVQg_z4Y335JMQrLfw5dj331Gqk2w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 286 bytes --]
also, if it makes you feel better, the yearly newlib release has already been
cut, so this will have ~1 year to bake and people lightly experiment before it
makes it into the next release. i know some folks do nightly builds from the
latest git trees as part of their own tests.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-19 23:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 4:47 [PATCH 0/8] newlib: convert newlib.h to autoheader Mike Frysinger
2022-01-18 4:47 ` [PATCH 1/8] newlib: internalize HAVE_INITFINI_ARRAY Mike Frysinger
[not found] ` <DM3P110MB0522248DFEE102BB37B43A8F9A589@DM3P110MB0522.NAMP110.PROD.OUTLOOK.COM>
2022-01-18 16:10 ` Fw: " C Howland
2022-01-19 0:53 ` Mike Frysinger
2022-01-19 2:39 ` C Howland
2022-01-19 3:44 ` Mike Frysinger
2022-01-19 23:50 ` Mike Frysinger [this message]
2022-01-18 4:47 ` [PATCH 2/8] newlib: merge acconfig.h changes into newlib.hin Mike Frysinger
2022-01-18 4:47 ` [PATCH 3/8] newlib: clean up autoheader templates Mike Frysinger
2022-01-18 4:47 ` [PATCH 4/8] newlib: sort newlib.h output Mike Frysinger
2022-01-18 4:47 ` [PATCH 5/8] newlib: move version defines out of the config headers Mike Frysinger
2022-01-18 4:47 ` [PATCH 6/8] newlib: add missing _NANO_MALLOC to newlib.hin Mike Frysinger
2022-01-18 4:47 ` [PATCH 7/8] newlib: iconv: autogenerate iconv define list Mike Frysinger
2022-01-18 4:47 ` [PATCH 8/8] newlib: switch newlib.h to autoheader Mike Frysinger
2022-01-19 14:51 ` [PATCH 0/8] newlib: convert " Corinna Vinschen
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=Yeiju1luBDTBJwu5@vapier \
--to=vapier@gentoo.org \
--cc=cc1964t@gmail.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).