summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn b/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn
index 80cb046d9..78f4977a2 100644
--- a/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn
+++ b/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn
@@ -19,4 +19,9 @@ on the drive.
* Check for any problems with the annexed data: `cd $good; git annex fsck`
* Now you can remove the corrupted repository, the new one is ready to use.
+Alternatively, recent versions of git-annex have a `git annex repair`
+command that uses <http://git-repair.branchable.com/> to repair a
+repository in-place. The git-annex assistant will detect most corruptions
+and offer to run the repair for you automatically.
+
--[[Joey]]