From: Mark Levedahl <mlevedahl@gmail.com>
To: Mikko Rapeli <mikko.rapeli@iki.fi>
Cc: cygwin@cygwin.com, git@vger.kernel.org
Subject: Re: Cygwin, git and x: directory
Date: Fri, 12 Jul 2013 11:27:14 -0400 [thread overview]
Message-ID: <51E02052.4050804@gmail.com> (raw)
In-Reply-To: <20130712124213.GL14578@lakka.kapsi.fi>
On 07/12/2013 08:42 AM, Mikko Rapeli wrote:
> (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:
I would report this on the Cygwin list, not here. Any use of dos file
paths using a Cygwin tool is not recommended, officially only POSIX
paths are supported. If cygwin's Cmake is generating dos style paths,
that is a bug that needs reporting to the Cygwin list. Also, I'm not
sure how the developers will react to mishandling a directory named x:,
but the behaviour you see is a limitation of the Cygwin platform, not of
git.
Mark
prev parent reply other threads:[~2013-07-12 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 12:42 Cygwin, git and x: directory Mikko Rapeli
2013-07-12 15:27 ` Mark Levedahl [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=51E02052.4050804@gmail.com \
--to=mlevedahl@gmail.com \
--cc=cygwin@cygwin.com \
--cc=git@vger.kernel.org \
--cc=mikko.rapeli@iki.fi \
/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).