On Thu, Oct 20, 2022, 8:16 PM W. Ekkehard Blanz <ekkehard.blanz@xxxxxxxxx> wrote: > Here is the output from running it with GIT_TRACE=1 (which I had to do under Cygwin, since this won't work in a DOS shell, but I am still using native git from Windows - did not install it in Cygwin to keep things consistent): > > $ GIT_TRACE=1 git clone 10.0.7.181:D:\\gitDepot\\test.git > 19:04:23.917439 exec-cmd.c:237 trace: resolved executable dir: D:/Applications/Git/mingw64/bin > 19:04:23.917439 git.c:460 trace: built-in: git clone '10.0.7.181:D:\gitDepot\test.git' > Cloning into 'test'... > 19:04:23.948681 run-command.c:655 trace: run_command: unset GIT_DIR; GIT_PROTOCOL=version=2 ssh -o SendEnv=GIT_PROTOCOL 10.0.7.181 'git-upload-pack '\''D:\gitDepot\test.git'\''' > username@10.0.7.181's password: > fatal: ''D:\gitDepot\test.git'' does not appear to be a git repository > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > > What I got from this is to use double backslashes to get the path right (I had tried this before though), but unfortunately, the result is still the same. Maybe try forward slash, it's valid in both unix and windows and sometimes plays nicer > I will try the power shell workaround once I am back from my doctor's appointment. Is that on the local or the remote machine or both? on the remote
