Windows上的msysGit’git clone’无法正常工作

目前使用msysgit(issue 136)的票证存在同样的问题,目前的解决方法是使用http而不是git地址进行克隆.

尝试的其他举措：

> GIT_TRACE = 1(并发布输出)
>尝试使用msysgit的其他版本或旧版本
>检查主计算机上是否存在任何防火墙/防病毒问题

这里切换到旧版本的msysgit可能是正确的选择：
见GitHub support thread：

Are you using the 1.6.4 prerelease of msysGit? There are known bugs with it.
We recommend a stable version,such as 1.6.0.

??
??谢谢克里斯,就是这样：在切换回以前版本的msysGit(Git-1.6.3.2-preview20090608.exe)后,问题不再发生了.

该问题实际上可能会影响任何Git1.6.4及更早版本：

git tries to check if the pack file exists by sending out a HEAD request,but chokes on the 500 error that some (if not all) github returns.

Using the repository used by the reporter:

$curl http://github.com/grails/grails.git/objects/info/packs
P pack-1290e84bed53bda28f0989dca48d836bd9104031.pack
P pack-bf40d38ae780512994e5127e832ed9d8853c186d.pack
P pack-f490d5f7d4671368f4a52c618ca9dce13b714ba1.pack
P pack-79e3a7f30e8989acc8403ac688be669a05384eef.pack

$curl -I http://github.com/grails/grails.git/objects/pack/pack-bf40d38ae780512994e5127e832ed9d8853c186d.pack
HTTP/1.1 500 Internal Server Error
Server: nginx/0.6.26
Date: Fri,04 Sep 2009 13:50:20 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Content-Length: 3193
Cache-Control: no-cache

见this thread.
GitHub支持团队目前正在调查此问题：

I don’t think the 500s are intentional,but there may be something odd with our setup that is causing them.
I have a ticket open to investigate the issue further. I have a feeling we won’t be messing with this till after the move,since it’s likely something with the server config.

Git1.6.4.4从9月16日开始执行contain a fix：

The workaround for Github server that sometimes gave 500 (Internal server error) response to HEAD requests in 1.6.4.3 introduced a regression that caused re-fetching projects over http to segfault in certain cases due to uninitialized pointer being freed.

但mssysgit尚未发布(9月21日)自7月底最初的1.6.4以来的任何新版本. (他们可能正在等待1.6.5或1.7)