From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/fsck-unexpected-type
Date: Fri, 01 Oct 2021 14:08:31 +0200 [thread overview]
Message-ID: <87y27dq70e.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqh7e18soj.fsf@gitster.g>
On Thu, Sep 30 2021, Junio C Hamano wrote:
[Forgot to adjust the subject for
https://lore.kernel.org/git/8735plrlql.fsf@evledraar.gmail.com/]
> * 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@gmail.com/;
I think it should be ready.
next prev parent reply other threads:[~2021-10-01 12:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 1:01 What's cooking in git.git (Sep 2021, #09; Thu, 30) Junio C Hamano
2021-10-01 6:20 ` en/removing-untracked-fixes [Was: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)] Elijah Newren
2021-10-01 8:51 ` Ævar Arnfjörð Bjarmason
2021-10-01 17:05 ` en/removing-untracked-fixes [ Junio C Hamano
2021-10-01 6:31 ` en/remerge-diff [Was: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)] Elijah Newren
2021-10-01 7:01 ` Jeff King
2021-10-01 12:05 ` What's cooking in git.git (Sep 2021, #09; Thu, 30) Ævar Arnfjörð Bjarmason
2021-10-01 12:08 ` Ævar Arnfjörð Bjarmason [this message]
2021-10-01 14:32 ` ab/parse-options-cleanup Ævar Arnfjörð Bjarmason
2021-10-01 14:35 ` ab/sanitize-leak-ci & more leak fixes soon-or-not Ævar Arnfjörð Bjarmason
2021-10-01 14:48 ` ab/refs-errno-cleanup Ævar Arnfjörð Bjarmason
2021-10-01 14:56 ` What's cooking in git.git (Sep 2021, #09; Thu, 30) Jeff Hostetler
2021-10-01 15:01 ` ab/align-parse-options-help & ab/help-config-vars Ævar Arnfjörð Bjarmason
2021-10-01 15:05 ` ab/lib-subtest Ævar Arnfjörð Bjarmason
2021-10-01 15:07 ` ab/config-based-hooks-1 Ævar Arnfjörð Bjarmason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y27dq70e.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).