Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sat, 7 May 2005 13:25:40 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: mkdir -p and network drives Message-ID: <20050507172540.GA14393@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <87k6mc1au3.fsf@penguin.cs.ucla.edu> <20050506204324.GJ29240@trixie.casa.cgf.cx> <8764xvbl2n.fsf@penguin.cs.ucla.edu> <20050507154332.GF11243@trixie.casa.cgf.cx> <427CF5F5.2030907@byu.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <427CF5F5.2030907@byu.net> User-Agent: Mutt/1.5.8i On Sat, May 07, 2005 at 11:08:05AM -0600, Eric Blake wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >According to Christopher Faylor on 5/7/2005 9:43 AM: >>>Which Bash bug is that? >> >> Bash is the most important program for which 'that chdir("//") is >> currently no different from chdir("/")'. > >Is that a bug in bash or in cygwin, though? The comments for cygwin >bash-2.05b-17 mention that a patch from Corinna Vinschen was applied to >avoid turning '/' into '//' when converting/checking path. There is no need to speculate that this is a "bug". You seemed to be reading this thread: http://sources.redhat.com/ml/cygwin-patches/2005-q2/msg00020.html where Pierre informs that we added a workaround in cygwin for bash. If bash 2.05b-17 has Corinna's fix then the workaround is no longer needed. I will remove the workaround and see if things work ok. cgf -- 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/