path: root/Documentation/git-fsck.txt
diff options
authorJohannes Schindelin <>2007-07-22 20:20:26 (GMT)
committerJunio C Hamano <>2007-07-22 22:59:27 (GMT)
commit16a7fcfe5e568b50ddebe2369600e71da67d1405 (patch)
treede76309328d1dd4c9863b1179ab121410f1cfbf1 /Documentation/git-fsck.txt
parentc4640fe8d9e25fd3e206a39233c71a6dbb68917e (diff)
fsck --lost-found: write blob's contents, not their SHA-1
When looking for a lost blob, it is much nicer to be able to grep through .git/lost-found/other/* than to write an inefficient loop over the file names. So write the contents of the dangling blobs, not their object names. Signed-off-by: Johannes Schindelin <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-fsck.txt')
1 files changed, 4 insertions, 2 deletions
diff --git a/Documentation/git-fsck.txt b/Documentation/git-fsck.txt
index 1a432f2..45c0bee 100644
--- a/Documentation/git-fsck.txt
+++ b/Documentation/git-fsck.txt
@@ -65,8 +65,10 @@ index file and all SHA1 references in .git/refs/* as heads.
Be chatty.
- Write dangling refs into .git/lost-found/commit/ or
- .git/lost-found/other/, depending on type.
+ Write dangling objects into .git/lost-found/commit/ or
+ .git/lost-found/other/, depending on type. If the object is
+ a blob, the contents are written into the file, rather than
+ its object name.
It tests SHA1 and general object sanity, and it does full tracking of
the resulting reachability and everything else. It prints out any