From: Mikko Rapeli <mikko.rapeli@iki.fi>
To: cygwin@cygwin.com
Cc: git@vger.kernel.org
Subject: Cygwin, git and x: directory
Date: Fri, 12 Jul 2013 15:42:13 +0300 [thread overview]
Message-ID: <20130712124213.GL14578@lakka.kapsi.fi> (raw)
(please Cc: me in replies, not subscribed to the lists)
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:
# create Windows X: drive, cygwin utils can work with both unix and dos style
# path names
$ mkdir c:/temp/bar
$ subst x: c:/temp/bar
$ touch x:/file.txt
$ ls x:/
file.txt
# clean git tree from non-tracked files
$ git clean -d -x -f
Removing x:/
# observe results, git did rm -rf on the X drive instead of the local
# directory named x:
$ ls
x:
$ file x\:
x:: directory
$ ls x:/
ls: cannot access x:/: No such file or directory
$ ls c:/temp/bar
ls: cannot access c:/temp/bar: No such file or directory
$ subst
X:\: => C:\temp\bar
In real life CMake created C: file in a build tree -- which is also a bug
but a separate one -- which resulted in obviously catastrophic results.
-Mikko
next reply other threads:[~2013-07-12 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 12:42 Mikko Rapeli [this message]
2013-07-12 15:27 ` Cygwin, git and x: directory Mark Levedahl
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=20130712124213.GL14578@lakka.kapsi.fi \
--to=mikko.rapeli@iki.fi \
--cc=cygwin@cygwin.com \
--cc=git@vger.kernel.org \
/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 NNTP newsgroup(s).