Re: git-clone removes destination path after permission deny
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Aug 16, 2018, 23:43 UTC
- Message-ID
- <20180816234324.GA66961@aiede.svl.corp.google.com>
- In-Reply-To
- <450A55F6-A4B8-4841-8814-FC7365EFE43E@gmail.com>
Hi,
Agis wrote:
> On 16 Aug 2018, at 15:08, Agis <agis.anast@gmail.com> wrote:
Show 5 quoted lines
>> $ mkdir foo >> $ git clone git@github.com:agis/private.git foo >> Cloning into 'foo'... >> Permission denied (publickey). >> fatal: Could not read from remote repository.
[...]
>> $ ls foo >> ls: cannot access 'foo': No such file or directory >> >> Is this expected behavior?
[...]
> Nevermind, this is does not happen in 2.18.0. Apparently it was > fixed somewhere between 2.11 and 2.18.
Indeed, this was fixed by v2.16.2~5^2 (clone: do not clean up directories we didn't create, 2018-01-02).
Cc-ing the author of that change (Peff) so he can meet a happy user of it. :)
Thanks and hope that helps, Jonathan