why did "git clone" stop after unpacking object:100%, done

Question

$ git fetch pb
remote: Counting objects: 9, done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 9 (delta 0), reused 3 (delta 0)
Unpacking objects: 100% (9/9), done.

So I can not clone any code from server. Could anyone help me?

Answer 1

On an empty repo, the fetch will do nothing else (as mentioned in "What does the output of git pull actually mean?").
It will update FETCH_HEAD.

Only a git pull would update local branch and the working tree.

But if the command hung after that, as illustrated by this tweet, it could be a GitHub status issue.

October 15, 2012

04:04 pm PST
GitHub Pages was down from 3:50-3:59 pm. We're investigating the cause.

October 14, 2012 – minor interruption occurred

02:55 am PST
All connectivity issues have been resolved.

02:47 am PST
We are investigating errors with GitHub.com and API 

Answer 2

I had this same problem. Found the answer here. Two options, one is the ugly way and involves Ctrl-c'ing when your pull freezes, then running git fsck and git merge on the dangling commit. But there's a better way, if it works, through a method on this blog which describes how to use CNTLM.

Git doesn't work well with NTLM proxies, which is what you'll have in most corporate environments. The solution is to setup a local proxy that redirects traffic, which is what CNTLM does.

Install CNTLM, modify the .ini file to inlcude your user id, domain, password, and proxy settings. Start the proxy, then run this in your Git Bash: git config --global http.proxy localhost:3128

Should now work!