Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <200008240226.TAA24201@ultra.franz.com>
To: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
cc: cygwin AT sources DOT redhat DOT com
Subject: Re: cvs 1.10.8 built w/cygwin 1.1.4 
In-reply-to: Your message of Wed, 23 Aug 2000 20:14:25 EDT.
             <39A468E1 DOT 400CD7E6 AT ece DOT gatech DOT edu> 
Date: Wed, 23 Aug 2000 19:26:18 -0700
From: Kevin Layer <layer AT franz DOT com>

>> There is no need to make any additional changes to cvs, nor to wait for
>> this bug to be fixed in the cvs distribution before adding cvs to latest
>> -- because the bug is NOT a cvs bug. It's a cygwin bug.  A fix (to
>> cygwin1.dll) has already been applied to the current development sources
>> of cygwin.
>> 
>> http://sources.redhat.com/ml/cygwin/2000-08/msg00507.html
>> 
>> I'm not going to bastardize cvs by putting in a workaround to a cygwin
>> bug, when the cygwin bug is (a) already fixed, and (b) merely annoying
>> but not functional -- that is, cvs still works properly but prints out
>> annoying error messages as it goes.

Sounds fine, to me.

>> When cygwin-1.1.5 is released these error messages should go away. 

Also dandy.

>> And
>> please don't pester the core team for 1.1.5; you can try one of the
>> daily snapshots instead (http://sources.redhat.com/cygwin/snapshots/)

I wouldn't think of pestering anyone.

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