From: "ddgjop+2hbgmlszz4.sharklasers.com via cygwin" <cygwin@cygwin.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: php 7.1 is way behind
Date: Thu, 28 Jun 2018 22:13:00 -0000 [thread overview]
Message-ID: <376dede73c2f3982f9a7a004227afef45c95@sharklasers.com> (raw)
By the way, php pledges support for 7.1 branch until December of 2019 (Security only after Dec 1, 2018). So it's reasonable that cygwin could stay with that for another year longer.
----
Sent using Sharklasers.com
Block or report abuse: https://www.sharklasers.com//abuse/?a=QlhzEgQOY7cMjxm9%2FjAcfRk%3D
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2018-06-28 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 22:13 ddgjop+2hbgmlszz4.sharklasers.com via cygwin [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-28 21:31 ddgjop+2hbgmlszz4.sharklasers.com via cygwin
2018-06-28 18:01 dd92zi+2d7t34pt5a.sharklasers.com via cygwin
2018-06-28 18:28 ` Yaakov Selkowitz
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=376dede73c2f3982f9a7a004227afef45c95@sharklasers.com \
--to=cygwin@cygwin.com \
--cc=ddgjop+2hbgmlszz4@sharklasers.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).