summaryrefslogtreecommitdiff
path: root/t/t7810-grep.sh
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2016-09-27 16:59:50 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-09-27 14:08:30 -0700
commit2edffef2337eae691a454a072e0f9b9538725317 (patch)
treeca5acc195c62c4983c01e1049637fc3b08f3e85c /t/t7810-grep.sh
parentFourth batch for 2.11 (diff)
downloadtgif-2edffef2337eae691a454a072e0f9b9538725317.tar.xz
tree-walk: be more specific about corrupt tree errors
When the tree-walker runs into an error, it just calls die(), and the message is always "corrupt tree file". However, we are actually covering several cases here; let's give the user a hint about what happened. Let's also avoid using the word "corrupt", which makes it seem like the data bit-rotted on disk. Our sha1 check would already have found that. These errors are ones of data that is malformed in the first place. Signed-off-by: David Turner <dturner@twosigma.com> Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t7810-grep.sh')
0 files changed, 0 insertions, 0 deletions