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]: chdir

From: "Pierre A. Humblet" <pierre at phumblet dot no-ip dot org>
To: cygwin-patches at cygwin dot com
Date: Thu, 06 May 2004 10:00:37 -0400
Subject: Re: [Patch]: chdir
References: <20040505002003.GA8846@coe.bosbc.com> <3.0.5.32.20040504200359.007fcec0@incoming.verizon.net> <20040505002003.GA8846@coe.bosbc.com> <3.0.5.32.20040505004236.007ff280@incoming.verizon.net> <20040505095134.GA6206@cygbert.vinschen.de> <3.0.5.32.20040505235853.00806100@incoming.verizon.net> <20040506094334.GV2201@cygbert.vinschen.de> <20040506123720.GB17511@cygbert.vinschen.de>
Reply-to: Pierre dot Humblet at ieee dot org

Corinna Vinschen wrote:
> Ooops:
> 
>   $ cd /
>   /: No such file or directory.

Oops, nothing to do with chdir. It's in the code that detects
file components consisting entirely of dots or spaces.

Something crossed my mind. Should we allow trailing dots and
spaces on managed mounts (and encode that)? After all the goal
is to be fully Unix like there. 
Not sure how to make that backward compatible.

Pierre

Follow-Ups:
- Re: [Patch]: chdir
  - From: Christopher Faylor
- Re: [Patch]: chdir
  - From: Pierre A. Humblet

References:
- Re: [Patch]: chdir
  - From: Christopher Faylor
- [Patch]: chdir
  - From: Pierre A. Humblet
- Re: [Patch]: chdir
  - From: Pierre A. Humblet
- Re: [Patch]: chdir
  - From: Corinna Vinschen
- Re: [Patch]: chdir
  - From: Pierre A. Humblet
- Re: [Patch]: chdir
  - From: Corinna Vinschen
- Re: [Patch]: chdir
  - From: Corinna Vinschen

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