Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 26 May 2005 07:39:14 -0400
From:	Jason Tishler <jason AT tishler DOT net>
To:	cygwin AT cygwin DOT com
Subject:	Re: Fetchmail: Cygwin socket read retry
Message-ID:	<20050526113914.GD3112@tishler.net>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20050526062930 DOT GA988 AT home> <20050526111953 DOT GB3112 AT tishler DOT net>
Mime-Version:	1.0
In-Reply-To:	<20050526111953.GB3112@tishler.net>
User-Agent:	Mutt/1.4.1i
X-IsSubscribed:	yes

On Thu, May 26, 2005 at 07:19:53AM -0400, Jason Tishler wrote:
> The above is a caused be a known Winsock issue:

The above should have been the following:

    The above is caused by a known Winsock issue:

Sigh... :,(

Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -