From: Gerald Pfeifer <gerald@pfeifer.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"Andrew Stubbs" <ams@codesourcery.com>,
"Tom de Vries" <tdevries@suse.de>,
"Thomas Schwinge" <thomas@codesourcery.com>,
"Martin Liška" <mliska@suse.cz>,
"Matthias Klose" <doko@ubuntu.com>
Subject: Re: [Patch] install.texi: Bump newlib version for nvptx + gcn
Date: Sat, 21 Jan 2023 12:58:02 +0100 (CET) [thread overview]
Message-ID: <c34dd82b-80c3-2ef5-4a77-c0a5d4f7f833@pfeifer.com> (raw)
In-Reply-To: <11d635d0-9798-5344-934b-969cb01974ba@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
On Sat, 21 Jan 2023, Tobias Burnus wrote:
> A new newlib version has been realized yesterday: newlib-4.3.0 (yearly
> snapshot)
:
> Comments? Suggestions? – If there are none, I intent to commit the patch
> as obvious.
Is it maybe a little tough to bump the minimal requirement to something
only released yesterday? Or is this not an issue looking at the use cases?
(Genuine question. Maybe nothing to worry at all.)
And, this predates your patch, in one instance we refer to Newlib (upper
case9, in the other to newlib (lower case). Would it make sense to
converge to one?
Not an objection to the patch - you are the expert - just two (naive)
questions.
Gerald
next prev parent reply other threads:[~2023-01-21 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 9:57 Tobias Burnus
2023-01-21 11:58 ` Gerald Pfeifer [this message]
2023-01-21 13:27 ` Tobias Burnus
2023-01-22 1:45 ` Gerald Pfeifer
2023-01-23 9:30 ` Tobias Burnus
2023-01-23 11:37 ` [wwwdocs] gcc-6: Consistently lower-case newlib (was: [Patch] install.texi: Bump newlib version for nvptx + gcn) Gerald Pfeifer
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=c34dd82b-80c3-2ef5-4a77-c0a5d4f7f833@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=ams@codesourcery.com \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=tdevries@suse.de \
--cc=thomas@codesourcery.com \
--cc=tobias@codesourcery.com \
/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).