Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 23 Dec 2004 10:10:49 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: ls -F // doesn't work Message-ID: <20041223151049.GE13179@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20041223103540 DOT GF317 AT cygbert DOT vinschen DOT de> <0I960027PKJYMT AT pmismtp02 DOT mcilink DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0I960027PKJYMT@pmismtp02.mcilink.com> User-Agent: Mutt/1.4.1i On Thu, Dec 23, 2004 at 08:04:45AM -0700, Mark Paulus wrote: >On Thu, 23 Dec 2004 11:35:40 +0100, Corinna Vinschen wrote: > > >>While you're right, it's not a good thing that ls // returns these >>error messages. I found a buglet in Cygwin which results in scanning >>the root directory accidentally in this situation. > >For us non-informed, commercial developers, would you care to >define "buglet"? Is it bigger than a bug, but smaller than a bugger? > >Also, can you elaborate on the fix a bit, so I can find the fix and apply it >to my "sandbox"? I'm not sure I want all of Chris' recent updates for the >trailing dots until he releases the revised sources to fix the problem in >it's entirety, but I am interested in seeing this issue taken care of. You don't have to ask developers for patches. You can see the changes either in CVS or, when a snapshot is released, on the snapshot pages. If you don't see it in CVS, then it is still being worked on and asking people for a work in progress and you don't want a work in progress. -- 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/