X-Spam-Check-By:	sourceware.org
From:	ericblake AT comcast DOT net (Eric Blake)
To:	cygwin AT cygwin DOT com
Subject:	Re: experimental coreutils-5.94-4
Date:	Tue, 28 Feb 2006 16:18:31 +0000
Message-Id:	<022820061618.27185.440477D700069FD600006A3122069997350A050E040D0C079D0A@comcast.net>
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

> On Feb 28 07:30, Eric Blake wrote:
> > This version fixes the coreutils bug in pwd when called from /, or from
> > anywhere in the // hierarchy.  [...]
> 
> What happened to the simple, but *always* working idea to call getcwd in
> pwd to evaluate the current working directory?  The new implementation
> looks a bit maniac.

Ergo, this is an *experimental* release!  I _purposefully_
crippled the working getcwd implementation to give the
readdir fallback code more exposure (and to root out
bugs in the coreutils fallback code).  When cygwin 1.5.20
comes out, I will remove the cripple, and /bin/pwd will
once again be a super-efficient call to getcwd.

-- 
Eric Blake

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