From 6d67245728bbbc07ad1eeaf5b3c49f64c6bbcd11 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 20 Nov 2013 15:14:20 -0400 Subject: 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. --- debian/changelog | 2 ++ 1 file changed, 2 insertions(+) (limited to 'debian') 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 Tue, 19 Nov 2013 17:16:56 -0400 -- cgit v1.2.3