Re: regarding fix on "git clone $there $here"

2018-05-09 Thread Leslie Wang
Thanks for the confirmation. It is very helpful! Best Regards Leslie Wang > On May 8, 2018, at 11:44 PM, Junio C Hamano wrote: > > Leslie Wang writes: > >> At 2.14.1 or 2.15.1, if I run command like >> - mkdir /tmp/111 >> - git clone g...@github.com:111/111 /tmp/111 >> >> because it will

Re: regarding fix on "git clone $there $here"

2018-05-08 Thread Junio C Hamano
Leslie Wang writes: > At 2.14.1 or 2.15.1, if I run command like > - mkdir /tmp/111 > - git clone g...@github.com:111/111 /tmp/111 > > because it will failure, then /tmp/111 will be removed automatically. Yes, this was a (longstanding) bug that nobody bothered to fix for a long time. As "git

Re: regarding fix on "git clone $there $here"

2018-05-08 Thread Jeff King
On Tue, May 08, 2018 at 10:25:58PM -0700, Leslie Wang wrote: > Recently we try to upgrade ubuntu from 17.10 to 18.04, then we found > one inconsistent behavior on git clone. > > At 2.14.1 or 2.15.1, if I run command like > - mkdir /tmp/111 > - git clone g...@github.com:111/111 /tmp/111 > > be

regarding fix on "git clone $there $here"

2018-05-08 Thread Leslie Wang
Dear git experts, Recently we try to upgrade ubuntu from 17.10 to 18.04, then we found one inconsistent behavior on git clone. At 2.14.1 or 2.15.1, if I run command like - mkdir /tmp/111 - git clone g...@github.com:111/111 /tmp/111 because it will failure, then /tmp/111 will be removed autom