DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=w1mKQ
	cIONfAcY4KsWII2a5gtDAAJPJUOTJqe+R+FLOcgplfvDDctnmm00e4Zo26HLdXAP
	jlPxt+xYKbHgVwYpelnYFR9IvUZexqKIufsYS8bZQNQGMvzgwMveWCbSWNptUhrC
	8aBu3z74q6PQc0BFw1hnrxu0kx1MXgSu9HUIEg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: lwp-request stopped working with snapshots
References: <877g025x6i.fsf@Rainer.invalid>	<20141014193408.GG2681@calimero.vinschen.de>
Date: Tue, 14 Oct 2014 21:41:58 +0200
In-Reply-To: <20141014193408.GG2681@calimero.vinschen.de> (Corinna Vinschen's	message of "Tue, 14 Oct 2014 21:34:08 +0200")
Message-ID: <87y4si4ewp.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Corinna Vinschen writes:
> lwp-request is one of the tools using connect to try if a former
> non-blocking connect worked.  This is ugly but, sigh, valid behaviour,

What should it be doing instead?  LWP upstream has switched to a new
maintainer recently IIRC, so it might be a good time to suggest a few
cleanups.

> The latest changes to the socket code didn't take this scenario into
> account.  I applied a fix and uploaded a new snashot to
> https://cygwin.com/snapshots/
>
> Please give it a try.

I sure will do this first thing tomorrow, thanks!


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
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