diff options
| author | Joey Hess <joeyh@debian.org> | 2013-11-22 11:16:03 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@debian.org> | 2013-11-22 11:16:03 -0400 |
| commit | 7e592e1d6ed5e0b25b37215da7558c6324688d6f (patch) | |
| tree | 75a86ff02e9311bcff817f2dcfe9b0a6ca1b5708 /git-repair.1 | |
| download | git-repair-7e592e1d6ed5e0b25b37215da7558c6324688d6f.tar.gz | |
git-repair (1.20131122) unstable; urgency=low
* Added test mode, which can be used to randomly corrupt test
repositories, in reproducible ways, which allows easy
corruption-driven-development.
* Improve repair code in the case where the index file is corrupt,
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.
* Fixed crashes on bad file encodings.
* Can now run 10000 tests (git-repair --test -n 10000 --force)
with 0 failures.
# imported from the archive
Diffstat (limited to 'git-repair.1')
| -rw-r--r-- | git-repair.1 | 37 |
1 files changed, 37 insertions, 0 deletions
diff --git a/git-repair.1 b/git-repair.1 new file mode 100644 index 0000000..146840f --- /dev/null +++ b/git-repair.1 @@ -0,0 +1,37 @@ +.TH +.SH NAME +git\-repair \- Fix a broken git repository +.PP +.SH SYNOPSIS +git\-repair [\-\-force] +.PP +.SH DESCRIPTION +This can fix a corrupt or broken git repository, which git fsck would +only complain has problems. +.PP +It does by deleting all corrupt objects, and retreiving all missing +objects that it can from the remotes of the repository. +.PP +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 +\fB\-\-force\fP option, since that rewrites history and throws out missing data. +Note that the \fB\-\-force\fP option never touches tags, even if they are no +longer usable due to missing data. +.PP +After running this command, you will probably want to run \fBgit fsck\fP 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. +.PP +Since this command unpacks all packs in the repository, you may want to +run \fBgit gc\fP afterwards. +.PP +.SH AUTHOR +Joey Hess <joey@kitenet.net> +.PP +<http://git\-repair.branchable.com/> +.PP +.PP |