Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Sun, 29 Apr 2001 20:17:00 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: difficult problem with symbolic link handling Message-ID: <20010429201700.A24130@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20010428130748 DOT A20706 AT redhat DOT com> <20010430001845 DOT A24200 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010430001845.A24200@cygbert.vinschen.de>; from vinschen@redhat.com on Mon, Apr 30, 2001 at 12:18:45AM +0200 On Mon, Apr 30, 2001 at 12:18:45AM +0200, Corinna Vinschen wrote: >Somehow your latest changes to path.cc break check_case. > >Try to start a shell with CYGWIN=... check_case=adjust > >and call `ls -ld .' > >Result: >ls: .: No such file or directory. Works fine for me, but that is somewhat besides the point. I was asking for feedback on whether this was a worthwhile path to follow not whether my particular implementation had bugs or not. I actually marked the previous revision of path.cc so that I could revert to the old way of doing things if people had problems. I assume that since you didn't object to the words that you've moved on to debugging the implementation. cgf