X-Spam-Check-By: sourceware.org Date: Tue, 28 Feb 2006 18:44:32 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: experimental coreutils-5.94-4 Message-ID: <20060228174432.GB27116@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <022820061618 DOT 27185 DOT 440477D700069FD600006A3122069997350A050E040D0C079D0A AT comcast DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <022820061618.27185.440477D700069FD600006A3122069997350A050E040D0C079D0A@comcast.net> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 16:18, Eric Blake wrote: > > 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. Uh, I see. Thanks. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/