David Turner <[email protected]> writes: > From: David Turner <[email protected]> > > Instead of dying when fsck hits a malformed tree object, log the error > like any other and continue. Now fsck can tell the user which tree is > bad, too. > > Signed-off-by: David Turner <[email protected]> > --- > fsck.c | 18 +++-- > t/t1450-fsck.sh | 17 ++++- > .../307e300745b82417cc1a903f875c7d22e45ef907 | 4 +
To prevent further headaches in this directory, can we have .gitattributes that tells us that everything in there are binary files? Something like the attached. The other object was transferred as a binary patch, but I have no faith in what I applied from your e-mail message for this file that went though latin-1 to utf-8 conversion X-<. t/t1450/bad-objects/.gitattributes | 1 + 1 file changed, 1 insertion(+) diff --git a/t/t1450/bad-objects/.gitattributes b/t/t1450/bad-objects/.gitattributes new file mode 100644 index 0000000..a173f27 --- /dev/null +++ b/t/t1450/bad-objects/.gitattributes @@ -0,0 +1 @@ +[0-9a-f]*[0-9a-f] -diff
