致命的:头对象不好 [英] fatal: bad object HEAD
本文介绍了致命的:头对象不好的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我试着运行 git fsck --full
,我得到:
检查对象目录:100%(256/256),完成。
错误:HEAD:无效的sha1指针15044de63184bed22f9be9f48fd63a3a7652eea4
错误:refs / heads / master不指向有效的对象!
公告:没有默认引用
悬挂一滴f4ffb48ece75b45ec593146216a2ecae5a5b2194
悬挂一滴f37ffd41d80a2d07258d0b8fa7118d236d480fc0
晃来晃去的blob f1ff1fa538a538d9085e573f60ad11e8e7f5395e
悬挂一滴f9ff6bdaf08fdbf9001ff44d2aa1a49092c20ad1
悬挂一滴f97f1a223ef3ca33f55d51ae25d98d3b5b2f9ece
解决方案
在我的情况中,我编辑了 .git / refs /遥控器/原点/ HEAD
。我无法获得 git update-ref
的工作,但这似乎是推荐的方式。
如果 git checkout(< branch> |< commit>)
不起作用,你应该尝试像 git update-ref HEAD ref: master
或者试着编辑 .git / HEAD
。
Can somebody help me to solve this problem. I had made a previous post about this but I couldn't solve it through those answers. Please help:)
I have tried to run git fsck --full
and I get :
Checking object directories: 100% (256/256), done.
error: HEAD: invalid sha1 pointer 15044de63184bed22f9be9f48fd63a3a7652eea4
error: refs/heads/master does not point to a valid object!
notice: No default references
dangling blob f4ffb48ece75b45ec593146216a2ecae5a5b2194
dangling blob f37ffd41d80a2d07258d0b8fa7118d236d480fc0
dangling blob f1ff1fa538a538d9085e573f60ad11e8e7f5395e
dangling blob f9ff6bdaf08fdbf9001ff44d2aa1a49092c20ad1
dangling blob f97f1a223ef3ca33f55d51ae25d98d3b5b2f9ece
解决方案
In my case, I edited .git/refs/remotes/origin/HEAD
. I couldn't get git update-ref
to work, but that seems to be the recommended way.
So if git checkout (<branch> | <commit>)
doesn't work, you should try something like git update-ref HEAD ref:master
or just try editing .git/HEAD
.
这篇关于致命的:头对象不好的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文