undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge branch 'jk/doc-fsck'

Browse Source 
* jk/doc-fsck:
  docs: brush up obsolete bits of git-fsck manpage

Conflicts:
	Documentation/git-fsck.txt
This commit is contained in:
Junio C Hamano 2011-12-22 11:27:27 -08:00
commit a4c628d71d
1 changed files with 8 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
Documentation/git-fsck.txt
View File

@ -81,30 +81,20 @@ index file, all SHA1 references in .git/refs/*, and all reflogs (unless
progress status even if the standard error stream is not progress status even if the standard error stream is not
directed to a terminal. directed to a terminal.
It tests SHA1 and general object sanity, and it does full tracking of DISCUSSION
the resulting reachability and everything else. It prints out any ----------
git-fsck tests SHA1 and general object sanity, and it does full tracking
of the resulting reachability and everything else. It prints out any
corruption it finds (missing or bad objects), and if you use the corruption it finds (missing or bad objects), and if you use the
'--unreachable' flag it will also print out objects that exist but '--unreachable' flag it will also print out objects that exist but that
that aren't reachable from any of the specified head nodes. aren't reachable from any of the specified head nodes (or the default
set, as mentioned above).
So for example
git fsck --unreachable HEAD \
$(git for-each-ref --format="%(objectname)" refs/heads)
will do quite a _lot_ of verification on the tree. There are a few
extra validity tests to be added (make sure that tree objects are
sorted properly etc), but on the whole if 'git fsck' is happy, you
do have a valid tree.
Any corrupt objects you will have to find in backups or other archives Any corrupt objects you will have to find in backups or other archives
(i.e., you can just remove them and do an 'rsync' with some other site in (i.e., you can just remove them and do an 'rsync' with some other site in
the hopes that somebody else has the object you have corrupted). the hopes that somebody else has the object you have corrupted).
Of course, "valid tree" doesn't mean that it wasn't generated by some
evil person, and the end result might be crap. git is a revision
tracking system, not a quality assurance system ;)
Extracted Diagnostics Extracted Diagnostics
--------------------- ---------------------