This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin and x: directory
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 15 Jul 2013 12:40:18 +0200
- Subject: Re: Cygwin and x: directory
- References: <0D835E9B9CD07F40A48423F80D3B5A7021D8E0FC at USA7109MB022 dot na dot xerox dot net>
- Reply-to: cygwin at cygwin dot com
On Jul 12 20:09, Nellis, Kenneth wrote:
> On 07/12/2013 08:42 AM, Mikko Rapeli wrote:
> > Hi Cygwin and git developers,
> > Does following scenario show signs of bugs in Cygwin and/or git?
> > # setup git repo
> > $ cd /tmp
> > $ mkdir foo && cd foo
> > $ git init
> > # create x: directory
> > $ mkdir x:
> > $ ls
> > x:
> IMHO, this makes an interesting problem (unrelated to git):
> Shell script prompts user for file name.
> User enters "x:".
> Script proceeds as follows:
> $ mkdir tmpdir
> $ touch tmpdir/x:
> $ # useful work done here
> $ rm -r tmpdir
> rm: cannot remove `tmpdir/x:': No such file or directory
> rm: cannot remove `tmpdir': Directory not empty
That's a problem of how recursive rm works. It chdir's into
the subdirs it's working on and then calls "x:" which is recognized
as drive prefix of a windows path. `rm ./x:' works as expected.
> It would seem that touch and rm are following different
> rules regarding how files may be named.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple