From: Andrey Repin <anrdaemon@freemail.ru>
To: Corinna Vinschen <cygwin@cygwin.com>
Subject: Re: Cygwin and x: directory
Date: Tue, 16 Jul 2013 03:45:00 -0000 [thread overview]
Message-ID: <923049647.20130716014645@mtu-net.ru> (raw)
In-Reply-To: <20130715104018.GB18483@calimero.vinschen.de>
Greetings, Corinna Vinschen!
> 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.
Or a file stream with empty name.
Which isn't allowed either, AFAIK.
> `rm ./x:' works as expected.
>> It would seem that touch and rm are following different
>> rules regarding how files may be named.
> No.
> Corinna
--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 15.07.2013, <23:42>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2013-07-15 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 20:45 Nellis, Kenneth
2013-07-15 11:13 ` Corinna Vinschen
2013-07-15 11:20 ` Adam Dinwoodie
2013-07-15 11:41 ` Corinna Vinschen
2013-07-16 3:45 ` Andrey Repin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=923049647.20130716014645@mtu-net.ru \
--to=anrdaemon@freemail.ru \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).