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:	Wed, 2 Feb 2005 10:28:04 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: /proc functionality; ls errors
Message-ID:	<20050202092804.GB7084@cygbert.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<41FC0A3E DOT 5020702 AT tlinx DOT org> <20050131091944 DOT GA18009 AT cygbert DOT vinschen DOT de> <42006C72 DOT 2050706 AT tlinx DOT org>
Mime-Version:	1.0
In-Reply-To:	<42006C72.2050706@tlinx.org>
User-Agent:	Mutt/1.4.2i

On Feb  1 22:00, linda w wrote:
> Cool - does that mean it was a bug and was fixed, or did it just
> happen to disappear due to some other improvement?  Either way...

It was a bug which just didn't show up with ls from the old fileutils.

> 'bout how long does it take till things go from CVS to a release,
> these days.

Usually within the same year.

>   I've tried twice to build from CVS, but never seem
> to have gotten a full build to run w/no errors (not to mention having
> a woefully inadequate machine to build such a project on...(sigh)).

Did you read http://cygwin.com/faq/faq_3.html#SEC104 lately?  Otherwise,
as Brian wrote, try a snapshot.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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 -