{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 冷血范 的问题《What use is the *.git extension when cloning a git》','https://www.manongdao.com/q-725633.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Commonly seen on GitHub and here on SO (Import existing source code to GitHub):
git@github.com:/youruser/somename.git
vs
git@github.com:/youruser/somename
I accidentally added a git remote without the *.git extension and it worked fine. I only noticed it after pushing up a new branch.
Is there any need for the *.git extension?
No, you can skip the
.git: the git repository hosting service (here GitHub, but you would find the same with gitolite, GitLab or Gitorious) usually knows how to find the full repository path from its name alone (without '.git')