On Thu, Sep 30 2021, Junio C Hamano wrote: [Forgot to adjust the subject for https://lore.kernel.org/git/8735plrlql.fsf@xxxxxxxxxxxxxxxxxxx/] > * ab/fsck-unexpected-type (2021-09-30) 17 commits > - fsck: report invalid object type-path combinations > - fsck: don't hard die on invalid object types > - object-file.c: stop dying in parse_loose_header() > - object-file.c: return ULHR_TOO_LONG on "header too long" > - object-file.c: use "enum" return type for unpack_loose_header() > - object-file.c: simplify unpack_loose_short_header() > - object-file.c: make parse_loose_header_extended() public > - object-file.c: return -1, not "status" from unpack_loose_header() > - object-file.c: don't set "typep" when returning non-zero > - cat-file tests: test for current --allow-unknown-type behavior > - cat-file tests: add corrupt loose object test > - cat-file tests: test for missing/bogus object with -t, -s and -p > - cat-file tests: move bogus_* variable declarations earlier > - fsck tests: test for garbage appended to a loose object > - fsck tests: test current hash/type mismatch behavior > - fsck tests: refactor one test to use a sub-repo > - fsck tests: add test for fsck-ing an unknown type > > "git fsck" has been taught to report mismatch between expected and > actual types of an object better. > > Will merge to 'next'? I re-rolled a v10 that hopefully gets rid of the last bugs in the recent updates: https://lore.kernel.org/git/cover-v10-00.17-00000000000-20211001T091051Z-avarab@xxxxxxxxx/; I think it should be ready.
