From: Jeff Johnston <jjohnstn@redhat.com>
To: Newlib <newlib@sourceware.org>
Subject: newlib-4.3.0 yearly snapshot created
Date: Fri, 20 Jan 2023 16:49:32 -0500 [thread overview]
Message-ID: <CAOox84tjkL4VUHCA5ZQ1FOk0KQv6BTat0XA+RYSHnaYANYdijQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
A bit later than usual, but I have posted a newlib yearly release snapshot
to the newlib ftp site. With Mike's changes to configuration/build it was
a very simple process: thanks Mike. It also is much smaller than last
year's 4.2.0 snapshot release.
For details on major changes, see the newlib NEWS file.
Thanks to everyone who contributed and of course, Corinna, for leading the
project and reviewing most of the patches.
-- Jeff J.
reply other threads:[~2023-01-20 21:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAOox84tjkL4VUHCA5ZQ1FOk0KQv6BTat0XA+RYSHnaYANYdijQ@mail.gmail.com \
--to=jjohnstn@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).