summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/git-recover-repository.mdwn40
1 files changed, 0 insertions, 40 deletions
diff --git a/doc/git-recover-repository.mdwn b/doc/git-recover-repository.mdwn
deleted file mode 100644
index dac4a310b..000000000
--- a/doc/git-recover-repository.mdwn
+++ /dev/null
@@ -1,40 +0,0 @@
-# NAME
-
-git-recover-repository - Fix a broken git repository
-
-# SYNOPSIS
-
-git-recover-repository [--force]
-
-# DESCRIPTION
-
-This can fix a corrupt or broken git repository, which git fsck would
-only complain has problems.
-
-It does by deleting all corrupt objects, and retreiving all missing
-objects that it can from the remotes of the repository.
-
-If that is not sufficient to fully recover the repository, it can also
-reset branches back to commits before the corruption happened, delete
-branches that are no longer available due to the lost data, and remove any
-missing files from the index. It will only do this if run with the
-`--force` option, since that rewrites history and throws out missing data.
-Note that the `--force` option never touches tags, even if they are no
-longer usable due to missing data.
-
-After running this command, you will probably want to run `git fsck` to
-verify it fixed the repository. Note that fsck may still complain about
-objects referenced by the reflog, or the stash, if they were unable to be
-recovered. This command does not try to clean up either the reflog or the
-stash.
-
-Since this command unpacks all packs in the repository, you may want to
-run `git gc` afterwards.
-
-# AUTHOR
-
-Joey Hess <joey@kitenet.net>
-
-<http://git-annex.branchable.com/>
-
-Warning: Automatically converted into a man page by mdwn2man. Edit with care