From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: MS Windows 8.1 EoL today
Date: Wed, 11 Jan 2023 16:33:17 -0700 [thread overview]
Message-ID: <a5e04e2e-9078-dbe4-96df-ead58578a5d3@Shaw.ca> (raw)
In-Reply-To: <7716352a-da15-b7a4-c94c-e2f4cdd72dab@Shaw.ca>
On 2023-01-11 9:22, Corinna Vinschen wrote:
> On Jan 10 14:42, Brian Inglis via Cygwin wrote:
>> As MS Windows 8.1 has gone EoL today:
>> https://learn.microsoft.com/en-us/lifecycle/products/windows-81?source=recommendations
>> with Chrome, Edge, and other product support also ending this month, is
>> Cygwin 3.4.3 also the last release to support that and equivalent server
>> releases, and should that be clarified on the web pages and announcements.
> There are no plans to drop 8.1 support any time soon, and all 3.4.x
> versions will continue to run on Windows 7 and later, as already
> outlined in basically all cygwin package announcements since Cygwin
> 3.3.0:
> https://cygwin.com/pipermail/cygwin-announce/2021-October/010268.html
> https://cygwin.com/pipermail/cygwin-announce/2022-December/010831.html
> Only the 3.4.3 release announcement is missing this info accidentally.
Thanks for the clarification.
I was just in touch with curl upstream to drop their Downloads web page Cygwin
x86 32 bit section, and clarify update availability, and was unsure whether that
EoL affected anything.
I will edit https://github.com/curl/curl-www/issues/216 to clarify that for
future searchers.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
prev parent reply other threads:[~2023-01-11 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 21:42 Brian Inglis
2023-01-11 9:22 ` Corinna Vinschen
2023-01-11 23:33 ` Brian Inglis [this message]
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=a5e04e2e-9078-dbe4-96df-ead58578a5d3@Shaw.ca \
--to=brian.inglis@shaw.ca \
--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).