From: Jason Thorpe <thorpej@me.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Kamil Rytarowski <n54@gmx.com>,
Gerald Pfeifer <gerald@pfeifer.com>,
Matthew Bauer <mjbauer95@gmail.com>,
libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org,
Jason Thorpe <thorpej@netbsd.org>,
Krister Walfridsson <krister.walfridsson@gmail.com>
Subject: Re: [PATCH] libstdcxx: Update ctype_base.h from NetBSD upstream
Date: Tue, 07 Jan 2020 20:44:00 -0000 [thread overview]
Message-ID: <00816D64-922B-4223-9DE1-50BB4F7FD665@me.com> (raw)
In-Reply-To: <20200107154313.GS490107@redhat.com>
> On Jan 7, 2020, at 7:43 AM, Jonathan Wakely <jwakely@redhat.com> wrote:
>
> For Jason and Krister's benefit, that last comment was referring to
> an earlier suggestion to not try to support old NetBSD releases, see
> https://gcc.gnu.org/ml/libstdc++/2020-01/msg00026.html
>
>> I think we need the netbsd target maintainers (CC'd) to decide whether
>> GCC should still support older releases or drop that support for GCC
>> 10. Usually I'd say we need a period of deprecation, but if GCC
>> doesn't currently build on NetBSD then maybe that's unnecessary.
The affected NetBSD versions are NetBSD 6 and earlier, which are EOL from the NetBSD perspective, so I think this is OK.
-- thorpej
next prev parent reply other threads:[~2020-01-07 20:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFnZKr1EPETS4CNu0rHwkhWSGRDt_e0TJpjUPTfSeDywDXyVRg@mail.gmail.com>
2019-12-21 23:37 ` Gerald Pfeifer
2019-12-22 14:06 ` Kamil Rytarowski
2019-12-23 10:33 ` Jonathan Wakely
2020-01-06 15:24 ` Jonathan Wakely
2020-01-06 22:20 ` Kamil Rytarowski
2020-01-07 0:26 ` Jonathan Wakely
2020-01-07 0:31 ` Kamil Rytarowski
2020-01-07 15:40 ` Jonathan Wakely
2020-01-07 15:43 ` Jonathan Wakely
2020-01-07 20:44 ` Jason Thorpe [this message]
2020-01-10 17:54 ` Jonathan Wakely
2020-01-14 16:56 ` Kamil Rytarowski
2020-01-14 21:25 ` Jason Thorpe
2020-01-16 17:47 ` Jonathan Wakely
2020-01-16 21:38 ` Jason Thorpe
2020-01-06 15:34 ` Jonathan Wakely
2020-01-06 23:19 ` Kamil Rytarowski
2020-01-07 0:28 ` Jonathan Wakely
2020-01-07 0:54 ` Kamil Rytarowski
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=00816D64-922B-4223-9DE1-50BB4F7FD665@me.com \
--to=thorpej@me.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jwakely@redhat.com \
--cc=krister.walfridsson@gmail.com \
--cc=libstdc++@gcc.gnu.org \
--cc=mjbauer95@gmail.com \
--cc=n54@gmx.com \
--cc=thorpej@netbsd.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).