This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch]: mkdir -p and network drives

From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
To: cygwin-patches at cygwin dot com
Date: Fri, 6 May 2005 11:13:25 -0400
Subject: Re: [Patch]: mkdir -p and network drives
References: <002f01c5523f$6d6f38b0$3e0010ac@wirelessworld.airvananet.com> <20050506142213.GA20565@trixie.casa.cgf.cx> <00a701c5524b$a66949b0$3e0010ac@wirelessworld.airvananet.com> <20050506145838.GD20565@trixie.casa.cgf.cx> <00b101c5524d$4b889990$3e0010ac@wirelessworld.airvananet.com>
Reply-to: cygwin-patches at cygwin dot com

On Fri, May 06, 2005 at 11:07:13AM -0400, Pierre A. Humblet wrote:
>That's not Paul Eggert's position,
>http://cygwin.com/ml/cygwin/2005-05/msg00251.html I don't expect
>problems with //, we had it working in cvs for a while and only bash
>had issues.  Program translating // to / should already have problems
>and they won't be affected if Cygwin keeps //

Hmm.  I missed that message.  Seems rather... uncooperative... to check in
a "fix" for Cygwin that wouldn't actually work on Cygwin.  I certainly
am enjoying the "Cygwin is broken so let's fix it!" implication, though.

cgf

References:
- Re: [Patch]: mkdir -p and network drives
  - From: Pierre A. Humblet
- Re: [Patch]: mkdir -p and network drives
  - From: Christopher Faylor
- Re: [Patch]: mkdir -p and network drives
  - From: Pierre A. Humblet
- Re: [Patch]: mkdir -p and network drives
  - From: Christopher Faylor
- Re: [Patch]: mkdir -p and network drives
  - From: Pierre A. Humblet

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]