使用git 1.6.4.2时，当我尝试git pull时，会出现以下错误：
error: unable to resolve reference refs/remotes/origin/LT558-optimize-sql: No such file or directory
From git+ssh://remoteserver/~/misk5
! [new branch] LT558-optimize-sql -> origin/LT558-optimize-sql (unable to update local ref)
error: unable to resolve reference refs/remotes/origin/split-css: No such file or directory
! [new branch] split-css -> origin/split-css (unable to update local ref)
我尝试过git远程梅干起源，但没用。
当前回答
$ rm .git/refs/remotes/origin/master
$ git fetch
来自bitbucket.org:xx/mkyong教程
df0eee8..3f7af90 master -> origin/master
$ git pull
已经是最新的。
其他回答
我只是想补充一下Git引用损坏的可能原因之一。
可能的根本原因
在我的系统（Windows 7 64位）上，当BSOD发生时，一些存储的参考文件（最有可能是BSOD发生后当前打开/写入的）会被NULL字符（ASCII 0）覆盖。
正如其他人提到的，要修复它，只需删除那些无效的引用文件并重新获取或重新提取存储库就足够了。
实例
错误消息：
无法锁定引用“refs/remotes/origin/some/branch”：无法解析引用“refs/remotes/origin/some/bbranch”：引用已断开
解决方案：
删除存储在文件%repo_root%/.git/refs/remotes/origin/some/branch中的引用refs/remotes/corigin/sme/branch。
我能够与
git remote update --prune
$ rm .git/refs/remotes/origin/master
$ git fetch
来自bitbucket.org:xx/mkyong教程
df0eee8..3f7af90 master -> origin/master
$ git pull
已经是最新的。
尝试使用以下方法清理本地存储库：
$ git gc --prune=now
$ git remote prune origin
man git gc（1）：
git-gc - Cleanup unnecessary files and optimize the local repository
git gc [--aggressive] [--auto] [--quiet] [--prune=<date> | --no-prune]
Runs a number of housekeeping tasks within the current repository, such as compressing file revisions
(to reduce disk space and increase performance) and removing unreachable objects which may have been
created from prior invocations of git add.
Users are encouraged to run this task on a regular basis within each repository to maintain good disk
space utilization and good operating performance.
man git远程（1）：
git-remote - manage set of tracked repositories
git remote prune [-n | --dry-run] <name>
Deletes all stale remote-tracking branches under <name>. These stale branches have already been
removed from the remote repository referenced by <name>, but are still locally available in
"remotes/<name>".
我在作曲家更新方面也遇到了同样的问题。但对我来说，只有在我清除了composer缓存并删除了供应商文件夹的内容后，它才起作用：
rm -rf vendor/*
git gc --prune=now
git pull
composer clear-cache
composer update my/package
