-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken commit 5e6ecdad9f69b1ff789a17733b8edc6fd7091bd8 #2690
Comments
No it isn't possible to repair the history. That will change the SHA value of every commit after it and update the timestamps on ALL of them. It will invalidate every tag since that commit and it will cause far too many headaches. |
The kwarg is named `headers`, not `header`. Also, its a dict, not a set.
To be clear, it is technically possible to repair this, also if repairing it didn't affect the repository's history from that point on, I would be very much in favor of it, but it irrevocably breaks expectations around our history and will cause more trouble than not. You appear to be the first person to have checked this and found it to be an issue. Even if |
Oh, really? I thought I'm just too lazy to find an old and closed issue. I just happen to have "transfer.fsckObjects = true" in my ~/.gitignore... @sigmavirus24, yep, this looks like a very popular repo. Forking just for one commit would be a solution, but... Ok, I'll just disable the checks in .git/config after the checkout. |
@anatolyborodin Recent versions of git ( |
"git fsck" thinks this commit is broken:
Would it be possible to repair the history?
The text was updated successfully, but these errors were encountered: