summaryrefslogtreecommitdiff
path: root/Git/Fsck.hs
Commit message (Collapse)AuthorAge
* fix reversion of bad fsck tryharder codeJoey Hess2013-11-20
|
* remove fsck tryharder codeJoey Hess2013-11-20
| | | | | | It turned out to be broken, and led to failures. 6d67245728bbbc07ad1eeaf5b3c49f64c6bbcd11 was a better fix for the problem that code tried to fix.
* fix a crashJoey Hess2013-11-20
|
* try to recover even if git fsck cannot be coaxed to tell us any bad objectsJoey Hess2013-11-20
| | | | | | | Sometimes git fsck outputs no shas even with --verbose, but fails, due to badly corrupt objects. The best thing to do in this situation is to try to pull and rsync from remotes, hoping that the bad objects will be overwritten.
* copied from git-annexJoey Hess2013-11-18