projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c4640fe) | patch
fsck --lost-found: write blob's contents, not their SHA-1
authorJohannes Schindelin <Johannes.Schindelin@gmx.de>
Sun, 22 Jul 2007 20:20:26 +0000 (21:20 +0100)
committerJunio C Hamano <gitster@pobox.com>
Sun, 22 Jul 2007 22:59:27 +0000 (15:59 -0700)
commit16a7fcfe5e568b50ddebe2369600e71da67d1405
treede76309328d1dd4c9863b1179ab121410f1cfbf1tree | snapshot
parentc4640fe8d9e25fd3e206a39233c71a6dbb68917ecommit | 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 <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-fsck.txt diff | blob | history
builtin-fsck.c diff | blob | history
Git—the stupid content tracker