summaryrefslogtreecommitdiff
path: root/t/t5100/info0010
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2012-07-28 11:06:29 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-07-29 15:14:08 -0700
commitc479d14a80743b1cb86d77695607f4c81f7d8797 (patch)
tree3da17f344439eceec6dbf8c8bc13fc923a8603e6 /t/t5100/info0010
parentdo not write null sha1s to on-disk index (diff)
downloadtgif-c479d14a80743b1cb86d77695607f4c81f7d8797.tar.xz
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>
Diffstat (limited to 't/t5100/info0010')
0 files changed, 0 insertions, 0 deletions