summaryrefslogtreecommitdiff
path: root/doc/index.mdwn
diff options
context:
space:
mode:
authorJoey Hess <joeyh@debian.org>2013-12-03 15:02:21 -0400
committerJoey Hess <joeyh@debian.org>2013-12-03 15:02:21 -0400
commitb1ed0aee347a88507d1530f61006cd658b57e54c (patch)
treeeb2a975663782f83e6b20d6d239447d7222de81b /doc/index.mdwn
parent7e592e1d6ed5e0b25b37215da7558c6324688d6f (diff)
parenta4f3e112954e1b785c84c339bcbd83597a89335e (diff)
downloadgit-repair-b1ed0aee347a88507d1530f61006cd658b57e54c.tar.gz
Record git-repair (1.20131203) in archive suite sid
Diffstat (limited to 'doc/index.mdwn')
-rw-r--r--doc/index.mdwn7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/index.mdwn b/doc/index.mdwn
index f880bc6..1d9a7a9 100644
--- a/doc/index.mdwn
+++ b/doc/index.mdwn
@@ -3,9 +3,14 @@
It is a complement to `git fsck`, which finds problems, but does not fix
them.
+As well as avoiding the need to rm -rf a damaged repository and re-clone,
+using git-repair can help rescue commits you've made to the damaged
+repository and not yet pushed out.
+
## download
- git clone git://git-repair.branchable.com/ git-repair
+* `git clone git://git-repair.branchable.com/ git-repair`
+* from [Hackage](http://hackage.haskell.org/package/git-repair)
## install