]> git.ipfire.org Git - thirdparty/git.git/commit - tree-walk.c
tree-walk: be more specific about corrupt tree errors
authorJeff King <peff@peff.net>
Tue, 27 Sep 2016 20:59:50 +0000 (16:59 -0400)
committerJunio C Hamano <gitster@pobox.com>
Tue, 27 Sep 2016 21:08:30 +0000 (14:08 -0700)
commit2edffef2337eae691a454a072e0f9b9538725317
treeca5acc195c62c4983c01e1049637fc3b08f3e85c
parent6fe1b1407ed91823daa5d487abe457ff37463349
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>
t/t1007-hash-object.sh
tree-walk.c