Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<39297FE4.237A823D@vinschen.de>
Date:	Mon, 22 May 2000 20:43:48 +0200
From:	Corinna Vinschen <corinna AT vinschen DOT de>
Reply-To:	cygwin <cygwin AT sourceware DOT cygnus DOT com>
Organization:	Cygnus Solutions, a Red Hat Company
X-Mailer:	Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686)
X-Accept-Language:	de, en
MIME-Version:	1.0
To:	earnie_boyd AT yahoo DOT com
CC:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: Weird patch problem + simple fix
References:	<20000522183237 DOT 23133 DOT qmail AT web122 DOT yahoomail DOT com>

Earnie Boyd wrote:
> --- Chris Faylor <cgf AT cygnus DOT com> wrote:
> > Ok.  This is a workaround.  I'm looking for insight into whether something
> > changed in Cygwin or not.
> 
> I remember this as a problem in b18.  I've not seen it since.  I know that it
> is specific to Win32 and had posted patches for patch years ago.  As for
> something changing in Cygwin to have caused the problem, if nothing was done to
> prevent it in b19, then no nothing changed.  If something was done in b19 to
> prevent, then, well, it's broke again.

I have already found the problem and checked in a patch
an hour ago so it should appear in the tonights developer
snapshot.

Corinna

-- 
Corinna Vinschen
Cygwin Developer
Cygnus Solutions, a Red Hat company

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -