From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: Re: [HEADSUP] Phasing out old Windows versions and 32 bit support
Date: Wed, 27 Oct 2021 09:07:49 -0400 [thread overview]
Message-ID: <51chng5g9tqvqiuf64u2mepqg3robr4s57@4ax.com> (raw)
In-Reply-To: <20211027092416.5541c44d36ba0d4a306fdf7d@nifty.ne.jp>
> On Tue, 26 Oct 2021 22:55:01 +0200
> Corinna Vinschen wrote:
> > We're also planning to drop Support for the 32 bit release of Cygwin in
> > 2022, thus Cygwin 3.4.0 won't come in 32 bit anymore, and the package
> > maintainers won't have to update 32 bit packages anymore. If you're
> > still running Cygwin under WOW64, consider to move to 64 bit in the next
> > couple of months.
>
> I agree with you that 32 bit cygwin under WOW64 is not worth to
> support any more. However, 32 bit version of Windows 10 will be
> still supported at least until Oct. 2025. Personally, I think it
> would not be nice to exclude the supported windows version from
> cygwin support.
On the one hand, it's not much more work to build packages for x86.
On the other hand, 32-bit Cygwin will still be available - it just won't be
updated, unless package maintainers want to. It's been many years since
32-bit PCs were sold. I don't know how many 32-bit PCs are still in use and
running Cygwin, but it can't be very many.
Overall, I agree that it's time.
next prev parent reply other threads:[~2021-10-27 13:08 UTC|newest]
Thread overview: 29+ 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 [this message]
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 ` EXTERNAL: " Damon Register
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
2021-10-27 20:36 [HEADSUP] Phasing out old Windows versions and 32 bit support Jeremy Drake
2021-10-28 6:00 ` Brian Inglis
2021-10-28 7:11 ` 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=51chng5g9tqvqiuf64u2mepqg3robr4s57@4ax.com \
--to=schulman.andrew@epa.gov \
--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).