Re: git-clone removes destination path after permission deny

Nevermind, this is does not happen in 2.18.0. Apparently it was fixed somewhere between 2.11 and 2.18. > On 16 Aug 2018, at 15:08, Agis wrote: > > Hello. > > I've recently observed the following: > >$ mkdir foo >$ # try to clone from a repository that you

git-clone removes destination path after permission deny

mote repository. Please make sure you have the correct access rights and the repository exists. $ ls foo ls: cannot access 'foo': No such file or directory Is this expected behavior? Thanks in advance, Agis P.S. If this is something that should be fixed, I'd be happy to prepare a patch