From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: cygwin 3.3.4?
Date: Fri, 28 Jan 2022 10:39:52 +0100 [thread overview]
Message-ID: <YfO56LXUHPYUmzvS@calimero.vinschen.de> (raw)
In-Reply-To: <7cdd611f-7ecf-e0cd-d67f-515636ec4546@towo.net>
On Jan 27 19:43, Thomas Wolff wrote:
> Am 27.01.2022 um 17:40 schrieb Corinna Vinschen:
> > On Jan 27 16:24, Thomas Wolff wrote:
> > > Am 27.01.2022 um 15:51 schrieb Corinna Vinschen:
> > > > Hey guys,
> > > >
> > > > Anything left for a 3.3.4 release?
> > > Well, hm, maybe a slight reconsideration of the deprecation policy?
> > 3.3.4 neither deprecates Vista, nor 32 bit. Read the deprecation notes
> > in the 3.3.3 announcement again ;)
> > https://cygwin.com/pipermail/cygwin/2021-December/250099.html
> Right, I confused 3.3.4 with 3.4 :/
> But still, can we perhaps drop Vista first and not drop 32-bit at the same
> time? Might also be better to respond to upcoming problems.
Dropping Vista is really just a side-job with only few code snippets
removed:
git log -p 7a3df8bb6fe3..a4efb2a6698f
git log -p -1 7ac0767053e2
We have next to no user and setup already warns users of Vista
that support for this OS is going to go away. Ripping out 32 bit
support is the really big thing for 3.4.
Corinna
next prev parent reply other threads:[~2022-01-28 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 14:51 Corinna Vinschen
2022-01-27 15:23 ` Ken Brown
2022-01-27 15:24 ` Thomas Wolff
2022-01-27 16:40 ` Corinna Vinschen
2022-01-27 18:43 ` Thomas Wolff
2022-01-28 9:39 ` Corinna Vinschen [this message]
2022-01-28 8:19 ` Takashi Yano
2022-01-28 10:37 ` Mark Geisert
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=YfO56LXUHPYUmzvS@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-developers@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).