diff options
| author | Joey Hess <joey@kitenet.net> | 2013-11-20 15:14:20 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-11-20 15:14:20 -0400 |
| commit | 6d67245728bbbc07ad1eeaf5b3c49f64c6bbcd11 (patch) | |
| tree | fb9fbeb6820e46eef37270a60704947e5aad4bed /debian | |
| parent | c2cd79e09b5aad1d634c58f5a130654649e25c49 (diff) | |
| download | git-repair-6d67245728bbbc07ad1eeaf5b3c49f64c6bbcd11.tar.gz | |
try to recover even if git fsck cannot be coaxed to tell us any bad objects
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.
Diffstat (limited to 'debian')
| -rw-r--r-- | debian/changelog | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog index e34606e..db190a7 100644 --- a/debian/changelog +++ b/debian/changelog @@ -7,6 +7,8 @@ git-repair (1.20131119) UNRELEASED; urgency=low and this hides other problems. * Write a dummy .git/HEAD if the file is missing or corrupt, as git otherwise will not treat the repository as a git repo. + * Improve fsck code to find badly corrupted objects that crash git fsck + before it can complain about them. -- Joey Hess <joeyh@debian.org> Tue, 19 Nov 2013 17:16:56 -0400 |