![]() ![]() Manually get the last two lines of the reflog: tail -n 2. Step 4: After deleting all of the empty files, I eventually came to git fsck actually running: git fsck -fullĮrror: HEAD: invalid sha1 pointer af9fc0c5939eee40f6be2ed66381d74ec2be895fĮrror: refs/heads/master does not point to a valid object!Įrror: refs/heads/master.u1conflict does not point to a valid object!Įrror: 0e31469d372551bb2f51a186fa32795e39f94d5c: invalid sha1 pointer in cache-treeĭangling blob 03511c9868b5dbac4ef1343956776ac508c7c2a2 Eventually Git started telling me it was actually doing something with the object directories: git fsck -fullĬhecking object directories: 100% (256/256), done.Įrror: object file. type f -empty -delete -print to remove all empty files. I figured what the heck it's blank anyway. Step 2: Run git fsck -full git fsck -fullĮrror: object file. git-old-2, etc.): cd ~/workspace/mcmc-chapter ![]() git (in fact I do this in between every step that changes something, but with a new copy-to name, e.g. To the Git wizards, if this was a bad way to fix it, please leave a comment. Ubuntu One is not a backup solution for Git it will helpfully overwrite your sane repository with your corrupted one.) My laptop ran out of battery during a Git operation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |