diff options
Diffstat (limited to 'doc/git-recover-repository.mdwn')
| -rw-r--r-- | doc/git-recover-repository.mdwn | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/git-recover-repository.mdwn b/doc/git-recover-repository.mdwn index f437e5688..dac4a310b 100644 --- a/doc/git-recover-repository.mdwn +++ b/doc/git-recover-repository.mdwn @@ -15,11 +15,12 @@ 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, and delete -branches that are no longer available due to the lost data. 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. +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 |