From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.11.0-0.1
Date: Thu, 16 Aug 2018 21:33:00 -0000 [thread overview]
Message-ID: <87bma2i06o.fsf@Rainer.invalid> (raw)
In-Reply-To: <announce.20180809202604.GN4180@calimero.vinschen.de> (Corinna Vinschen's message of "Thu, 9 Aug 2018 22:26:04 +0200")
Corinna Vinschen writes:
> I uploaded a new Cygwin test release 2.11.0-0.1
>
> I'm planning for a release end of August. Please test.
I've tested it for about a week now and have released for my other users
this week. This release actually fixed two problem I've encountered on
my new Server 2016 machine, both of which looked like races and have
evaded analysis since things worked both when straced and run in the
debugger. I have no idea which of the changes fixed that, though.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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
prev parent reply other threads:[~2018-08-16 19:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 20:27 Corinna Vinschen
2018-08-10 0:05 ` Andrey Repin
2018-08-10 11:05 ` Houder
2018-08-10 11:43 ` Corinna Vinschen
2018-08-10 12:43 ` Houder
2018-08-13 7:47 ` Corinna Vinschen
2018-08-13 8:03 ` Houder
2018-08-13 8:23 ` Corinna Vinschen
2018-08-13 21:29 ` Houder
2018-08-13 22:16 ` Eric Blake
2018-08-13 22:26 ` Houder
2018-08-14 6:09 ` john doe
2018-08-13 22:16 ` Houder
2018-08-14 9:50 ` Corinna Vinschen
2018-08-14 11:38 ` Houder
2018-08-13 20:27 ` Achim Gratz
2018-08-10 16:01 ` Marco Atzeri
2018-08-13 7:48 ` Corinna Vinschen
2018-08-13 8:36 ` Thomas Wolff
2018-08-13 11:25 ` Corinna Vinschen
2018-08-16 21:33 ` Achim Gratz [this message]
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=87bma2i06o.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).