| commit | c479d14a80743b1cb86d77695607f4c81f7d8797 | |
| author | Jeff King <peff@peff.net> | |
| Sat, 28 Jul 2012 15:06:29 +0000 (28 11:06 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sun, 29 Jul 2012 22:14:08 +0000 (29 15:14 -0700) | ||
| tree | 3da17f344439eceec6dbf8c8bc13fc923a8603e6 | treesnapshot (tar.gz zip) |
| parent | 4337b5856f88f18da47c176e3cbc95a35627044c | commitdiff |
fsck: detect null sha1 in tree entries
Short of somebody happening to beat the 1 in 2^160 odds of
actually generating content that hashes to the null sha1, we
should never see this value in a tree entry. So let's have
fsck warn if it it seen.
As in the previous commit, we test both blob and submodule
entries to future-proof the test suite against the
implementation depending on connectivity to notice the
error.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Short of somebody happening to beat the 1 in 2^160 odds of
actually generating content that hashes to the null sha1, we
should never see this value in a tree entry. So let's have
fsck warn if it it seen.
As in the previous commit, we test both blob and submodule
entries to future-proof the test suite against the
implementation depending on connectivity to notice the
error.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| fsck.c | diffblobblamehistory | |
| t/t1450-fsck.sh | diffblobblamehistory |