From: Agis <agis.anast@gmail.com>
Date: Thu, 16 Aug 2018 12:16:20 GMT
Subject: Re: git-clone removes destination path after permission deny
Message-ID: <450A55F6-A4B8-4841-8814-FC7365EFE43E@gmail.com>
In-Reply-To: <A1C23FEE-55CC-4888-9BD5-1C4566E83A38@gmail.com>

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 <agis.anast@gmail.com> wrote:
> 
> Hello.
> 
> I've recently observed the following:
> 
>    $ mkdir foo
>    $ # try to clone from a repository that you have no access to
>    $ git clone git@github.com:agis/private.git foo
>    Cloning into 'foo'...
>    Permission denied (publickey).
>    fatal: Could not read from remote 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
>