aboutsummaryrefslogtreecommitdiff
path: root/Git/Fsck.hs
Commit message (Collapse)AuthorAge
* Assistant, repair: Fix ignoring of git fsck errors due to duplicate file ↵Gravatar Joey Hess2016-10-31
| | | | entries in tree objects.
* Assistant, repair: Improved filtering out of git fsck lines about duplicate ↵Gravatar Joey Hess2016-10-18
| | | | file entries in tree objects.
* Assistant, repair: Filter out git fsck lines about duplicate file entries in ↵Gravatar Joey Hess2016-09-05
| | | | tree objects.
* update my email address and homepage urlGravatar Joey Hess2015-01-21
|
* export CreateProcess fields from Utility.ProcessGravatar Joey Hess2014-06-10
| | | | update code to avoid cwd and env redefinition warnings
* fully fix fsck memory use by iterative fsckingGravatar Joey Hess2014-03-12
| | | | Not very well tested, but I'm sure it doesn't eg, loop forever.
* read stdout and stderr concurrentlyGravatar Joey Hess2014-03-12
| | | | Avoids any buffering-related blocking.
* Improve memory usage when git fsck finds a great many broken objects.Gravatar Joey Hess2014-03-10
| | | | | | | | | From 1.7 gb to 900 mb on 300 thousand unique reported shas. When shas are not unique, this streams much better than before, so won't buffer the full list before putting them into the Set and throwing away dups. And when fsck output includes ignorable lines, especially dangling object lines, they won't be buffered in memory at all.
* remove Read instance for RefGravatar Joey Hess2014-02-19
| | | | | | | | Removed instance, got it all to build using fromRef. (With a few things that really need to show something using a ref for debugging stubbed out.) Then added back Read instance, and made Logs.View use it for serialization. This changes the view log format.
* repair: Check git version at run time.Gravatar Joey Hess2014-01-21
|
* repair: Support old git versions from before git fsck --no-dangling was ↵Gravatar Joey Hess2014-01-13
| | | | implemented.
* Improve repair of git-annex index file.Gravatar Joey Hess2013-12-10
| | | | | | | | | | Fixes a test case I received where a corrupted repo was repaired, but the git-annex branch was not. The root of the problem was that the MissingObject returned by the repair code was not necessarily a complete set of all objects that might have been deleted during the repair. So, stop trying to return that at all, and instead make the index file checking code explicitly verify that each object the index uses is present.
* assistant: Batch jobs are now run with ionice and nocache, when those ↵Gravatar Joey Hess2013-12-01
| | | | commands are available.
* merge improved fsck types from git-repair and some associated changesGravatar Joey Hess2013-11-30
|
* merge from git-repairGravatar Joey Hess2013-11-21
|
* merge from git-repairGravatar Joey Hess2013-11-21
|
* merge from git-repairGravatar Joey Hess2013-11-20
|
* merge from git-repairGravatar Joey Hess2013-11-20
|
* add git fsck to cronner, and UI for repository repair (not yet wired up)Gravatar Joey Hess2013-10-22
|
* make git fsck batch-capableGravatar Joey Hess2013-10-22
|
* implemented removal of corrupt tracking branchesGravatar Joey Hess2013-10-21
| | | | | | Oh, git, you made this so hard. Not determining if a branch pointed to some corrupt object, that was easy, but dealing with corrupt branches using git plumbing is a PITA.
* git-recover-repository 1/2 doneGravatar Joey Hess2013-10-20