From: Damon Register <damon.w.register@lmco.com>
To: <cygwin@cygwin.com>
Subject: Re: EXTERNAL: Re: [HEADSUP] Phasing out old Windows versions and 32 bit support
Date: Wed, 27 Oct 2021 13:22:02 -0400 [thread overview]
Message-ID: <4b2f060a-7961-fb34-0bf6-0eb218404b95@lmco.com> (raw)
In-Reply-To: <CAK-n8j5MWNdNtGz1Q_yEJs_WxT_=_tUXSWFsp_EkK4z90ORMpA@mail.gmail.com>
On 10/27/2021 11:25 AM, Jim Reisert AD1C wrote:
> On Tue, Oct 26, 2021 at 2:55 PM Corinna Vinschen wrote:
>
>> The upcoming version 3.3.0 is the last version officially supporting
>> Windows Vista and Windows Server 2008.
>>
>> The next major release 3.4.0 will be released in 2022 and will be the
>> last one officially supporting Windows 7, Windows 8, Windows Server 2008
>> R2, and Windows Server 2012.
>>
>> We're also planning to drop Support for the 32 bit release of Cygwin in
>> 2022
>
> This is all good. I really appreciate all the developer's efforts
> with Cygwin. There are thousands of ham radio operators all over the
> world who would not be getting data file updates without this
> software!
I am not sure that I follow this. Are you saying that amateur radio
users will be fine with the loss of old Windows support? The
appreciation is a general thanks for all that Cygwin developers
do or is it a hint that you hope they don't drop old Windows?
If it is the hope that old Windows isn't dropped, then it makes
me smile a little. Now that I am in amateur radio, I see that
it is an expensive hobby and a new computer is a small cost
compared to the radio equipment
Damon Register
KK4OFV
next prev parent reply other threads:[~2021-10-27 17:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 20:55 Corinna Vinschen
2021-10-26 22:01 ` [QUAR] " Eliot Moss
2021-10-26 22:52 ` Michel LaBarre
2021-10-27 4:29 ` Peter A. Castro
2021-10-27 8:53 ` Corinna Vinschen
2021-10-27 16:28 ` Peter A. Castro
2021-10-28 7:00 ` Corinna Vinschen
2021-10-27 14:57 ` Michel LaBarre
2021-10-27 16:38 ` Peter A. Castro
2021-10-27 8:33 ` Corinna Vinschen
2021-10-27 0:24 ` Takashi Yano
2021-10-27 8:49 ` Corinna Vinschen
2021-10-27 9:37 ` Thomas Wolff
2021-10-27 10:20 ` Corinna Vinschen
2021-10-27 16:46 ` Peter A. Castro
2021-10-27 21:04 ` Thomas Wolff
2021-10-27 23:35 ` Peter A. Castro
2021-10-27 13:07 ` Andrew Schulman
2021-10-27 11:03 ` L A Walsh
2021-10-27 11:10 ` Corinna Vinschen
2021-10-27 15:25 ` [HEADSUP] " Jim Reisert AD1C
2021-10-27 17:22 ` Damon Register [this message]
2021-10-27 22:35 ` [HEADSUP] Phasing out old Windows versions and 32 bit support [XEmacs for 64-bit?] Dan Harkless
2021-10-27 22:37 ` Dan Harkless
2021-10-27 22:36 ` Dan Harkless
2021-10-28 8:47 ` Henry S. Thompson
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=4b2f060a-7961-fb34-0bf6-0eb218404b95@lmco.com \
--to=damon.w.register@lmco.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).