From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.6
Date: Thu, 05 Nov 2015 19:19:00 -0000 [thread overview]
Message-ID: <87611gl0gk.fsf@Rainer.invalid> (raw)
In-Reply-To: <20151105175844.GC20857@calimero.vinschen.de> (Corinna Vinschen's message of "Thu, 5 Nov 2015 18:58:44 +0100")
Corinna Vinschen writes:
>> I (hopefully) fixed the issue and uploaded yet another developer
>> snapshot to https://cygwin.com/snapshots/ (with ACL changes again).
>
> Hang on for a while, I forgot to push the changes upstream before
> creating the snapshot. Try in half an hour or so.
CYGWIN_NT-6.3-WOW Cygwin 2.3.0(0.291/5/3) 2015-11-05 18:01 i686 Cygwin
CYGWIN_NT-6.3 Cygwin 2.3.0(0.291/5/3) 2015-11-05 18:02 x86_64 Cygwin
These two snapshots fix the failures (which as you said had just moved
from semi-random to predictable with the changes in signal handling).
Thanks!
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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:[~2015-11-05 19:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 9:42 Corinna Vinschen
2015-11-04 18:36 ` Achim Gratz
2015-11-04 21:07 ` Achim Gratz
2015-11-04 21:26 ` Achim Gratz
2015-11-05 9:24 ` Corinna Vinschen
2015-11-05 17:55 ` Corinna Vinschen
2015-11-05 17:58 ` Corinna Vinschen
2015-11-05 19:19 ` Achim Gratz [this message]
2015-11-06 0:28 ` Jan Bruun Andersen
2015-11-06 8:48 ` Corinna Vinschen
2015-11-06 17:30 ` Jan Bruun Andersen
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=87611gl0gk.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).