From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Last Version of Cygwin for XP
Date: Sat, 13 Feb 2016 17:20:00 -0000 [thread overview]
Message-ID: <20160213172044.GB8374@calimero.vinschen.de> (raw)
In-Reply-To: <CACoZoo1J1sOA+X30rbKXsCWgV-2gwqibNyr+_KZcuOOngvEnAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On Feb 12 16:58, Erik Soderquist wrote:
> On Fri, Feb 12, 2016 at 2:20 PM, Warren Young wrote:
> > The last time this topic came up, I came away with the impression that the only reason Cygwin hasn’t jettisoned XP support yet is that it’s more work than ignoring that old code.
>
> I have the same impression. Perhaps Corinna can confirm that?
Basically, yes. The next version of Cygwin will still run under XP with
a high likelyhood since I didn't remove any code yet, and I didn't addd
any OS function calls not available on XP.
However, I don't test on XP or 2K3 anymore, and I'll mostly ignore bug
reports related to running under XP in future. As soon as a new version
of Cygwin won't run on XP/2K3 anymore, I'll let everyone know early
enough.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-13 17:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 1:37 Jonathan Brenster
2016-02-10 2:17 ` Yaakov Selkowitz
2016-02-10 17:14 ` LMH
2016-02-10 17:24 ` Yaakov Selkowitz
2016-02-11 18:09 ` cyg Simple
2016-02-12 19:20 ` Warren Young
2016-02-12 21:58 ` Erik Soderquist
2016-02-12 22:42 ` Warren Young
2016-02-13 0:37 ` Erik Soderquist
2016-02-13 17:41 ` Tony Kelman
2016-02-14 0:41 ` Erik Soderquist
2016-02-15 14:53 ` Eric Blake
2016-02-13 17:20 ` Corinna Vinschen [this message]
2016-02-10 2:20 ` Andrey Repin
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=20160213172044.GB8374@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).