Greetings, Adam Dinwoodie! > Personally, I don't see this as a bug; AIUI using Windows style paths > isn't something that is supported in general in Cygwin, even if it's > something that works in some circumstances. I acknowledge that this > causes problems for non-Cygwin tools using Cygwin Git, but the > solution there is to either use Cygwin aware/native versions of those > tools, or to use non-Cygwin versions of Git.
The problem with Git is that it relies on entire POSIX ecosystem, contrary to, say, Subversion, which is just one drop-in binary. > In particular, I'm wary of fixing this set of interop problem > introducing some other problem; I'd prefer Cygwin tools to fail to > handle Windows paths entirely than the current situation where "c:" > refers to a file of that exact name in the current directory, and > "c:\" sometimes refers to a completely different directory, when on > *nix systems in general both would refer to files in the current > directory. Then it would just make Cygwin as useless as WSL. > I see you've raised this on the Git mailing list as well, and if the > upstream Git package starts to handle such paths, I'll take the > relevant patches. However since I don't consider this a bug, I'm not > going to raise it myself. -- With best regards, Andrey Repin Tuesday, November 27, 2018 17:33:24 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
