Local git repository does not exist after sucessfull clone when used from cygwin ssh/bash

[olivergondza]

git clone fail to create the target directory silently (more details in [1]). I am not sure if this use-case is supported, though. It works correctly from git bash shipped with Git for Windows.

[1] http://stackoverflow.com/questions/34266571/local-git-repository-does-not-exist-after-sucessfull-clone

[olivergondza]

For the sake of completeness, I tried to reproduce in powershell and it (had the same problem as cygwin bash and) revealed the culprit a bit. Absolute paths like /cygdrive/c/User/x cause git to actually manipulate the content of C:\cygdrive\c\User\x.

[kostix]

I'm not quie sure what this bug report is about.

You mean you're trying to clone on Windows into /tmp/targetDirectory, and it

1. Works in Git Bash;
2. Does not work in other shells (you have tried PowerShell).

Is my summary correct?

Having special treatment for names like /c/foo/bar is sensible but what /tmp/foo would be mapped to? C:\WINDOWS\TEMP\foo?

[olivergondza]

I come across this problem in cygwin where /tmp/foo is a valid, frequently used path. It seems that all the paths starting with / have that problem (/cygdrive/c/). I was not able to find out if cygwin (and its paths) is supported or not.

[kostix]

@olivergondza, Git for Windows has nothing to do with Cygwin: it uses no part of its runtime and is generally unaware about the very Cygwin existence.

GfW uses MinGW for building, and some bits of it (notably some tools, ported from Unix -- such as bash and perl) use the MSYS2 runtime which is a fork of MSYS which is a fork of Cygwin. Note that that latter fork happened very very long time ago and MSYS had (and has) very different goals from those of Cygwin.

You might check this -- especially see the point 6 in the "Runtime" section.

[dscho]

While Git for Windows ships with a modified version of Cygwin, it is not expected to interact well with software that records paths other than Windows ones (i.e. Cygwin's POSIX paths).

[olivergondza]

@dscho, @kostix, thanks for clarification.