From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Question about XP support
Date: Wed, 25 May 2016 20:03:00 -0000 [thread overview]
Message-ID: <20160525145450.GA8416@calimero.vinschen.de> (raw)
In-Reply-To: <CANnLRdiVTzJ_+VA=D7E=xmWwq0V+j0EvTxN2LNN=1CC65pg-+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
On May 25 09:56, Stephen John Smoogen wrote:
> On 25 May 2016 at 06:07, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> > On May 24 20:38, Herbert Stocker wrote:
> >> On 24.05.2016 18:44, Jim Reisert AD1C wrote:
> >> > I thought that support for Windows XP had been removed from Cygwin.
> >>
> >> No, has not yet been removed.
> >> And i'm sooo happy about this.
> >
> > Uh oh, bad timing...
> >
> > The next release 2.5.2 introduces the first non-XP compatible code.
> > It's in a seldom used corner of the code and it doesn't require
> > functions unavailable on XP, so it will very likely not break 99% of the
> > existing applications yet.
> >
> > But the next release after will very likely break XP support entirely.
>
> Would this be something to move to 3.x because there seems to be a lot
> of people who come onto the list a lot. That way they know they can
> use 2.5.1 and that is the last 'stable' release they need to 'fork'
> from as say Cygnus-XP1 to keep going?
The XP-breaking release will certainly be a major release. I doubt it's
called 3.0, though. 2.6 is more likely.
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-05-25 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 20:04 Jim Reisert AD1C
2016-05-25 0:51 ` Erik Soderquist
2016-05-25 0:58 ` Erik Soderquist
2016-05-25 6:11 ` Jim Reisert AD1C
2016-05-25 2:29 ` Herbert Stocker
2016-05-25 14:55 ` Corinna Vinschen
2016-05-25 16:09 ` Stephen John Smoogen
2016-05-25 17:46 ` Erik Soderquist
2016-05-26 1:32 ` Corinna Vinschen
2016-05-26 10:23 ` Erik Soderquist
2016-05-25 20:03 ` Corinna Vinschen [this message]
2016-05-29 16:56 ` Thomas Wolff
2016-05-30 8:45 ` Corinna Vinschen
[not found] ` <aa3ec6be-c001-bc00-2933-f20b190453fd@glocalnet.net>
2016-07-01 12:37 ` help Unsubscribe Eva Axehult
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=20160525145450.GA8416@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).