From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.8
Date: Fri, 18 Mar 2016 20:58:00 -0000 [thread overview]
Message-ID: <56EC6BDA.7050505@cornell.edu> (raw)
In-Reply-To: <announce.20160318203409.GA11113@calimero.vinschen.de>
On 3/18/2016 4:34 PM, Corinna Vinschen wrote:
> I released a new Cygwin TEST version 2.5.0-0.8.
>
> If things are not going very wrong, this is basically what you'll
> get as 2.5.0-1 release. Please, please test and report regressions.
Does this release include Yaakov's overhaul of the feature test macros?
If so, it might be a good idea for maintainers to test that nothing
unexpected happens when they build their packages.
Ken
--
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 prev parent reply other threads:[~2016-03-18 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 20:35 Corinna Vinschen
2016-03-18 20:58 ` Ken Brown [this message]
2016-03-18 21:03 ` Chris Sutcliffe
2016-03-18 21:23 ` Yaakov Selkowitz
2016-03-18 21:45 ` Corinna Vinschen
2016-03-22 15:16 ` Chris Sutcliffe
2016-03-22 16:03 ` 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=56EC6BDA.7050505@cornell.edu \
--to=kbrown@cornell.edu \
--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).