From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [EXTERNAL] Re: gcc -pg broken after cygwin update?
Date: Thu, 8 Dec 2022 10:40:33 +0100 [thread overview]
Message-ID: <Y5GxEXqZvugk8MOQ@calimero.vinschen.de> (raw)
In-Reply-To: <DM8PR09MB709570613F6E973561F071B6A51A9@DM8PR09MB7095.namprd09.prod.outlook.com>
On Dec 7 17:59, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > contains patches dropping W7 and W8 support:
>
> Hmm... I understood that "dropping support" was not something that
> would _require_ newer OS, but that it may not work (or not guaranteed
> to work, patches not checked for compatibility, etc) on the older
> OSes... Are you saying that W7 and W8 would be actively rejected?
Supporting older OSes requires to keep workarounds in the code and
sometimes leads to the inability to implement stuff in ways only
available on newer OSes.
Each deprecation of older OSes in Cygwin worked like this so far, and
for 3.5 (late 2023) we announced the deprecation of Windows 7 and 8
since the first 3.3.0 release in October 2021.
Corinna
next prev parent reply other threads:[~2022-12-08 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 8:58 Daniel Abrahamsson
2022-12-07 11:50 ` Corinna Vinschen
2022-12-07 12:40 ` Corinna Vinschen
2022-12-07 15:05 ` Daniel Abrahamsson
2022-12-07 15:09 ` Corinna Vinschen
2022-12-07 14:47 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-07 15:07 ` Corinna Vinschen
2022-12-07 17:59 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-08 9:40 ` Corinna Vinschen [this message]
2022-12-08 14:47 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-08 15:32 ` Corinna Vinschen
2022-12-08 16:02 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-12-08 16:06 ` 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=Y5GxEXqZvugk8MOQ@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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).