From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>,
Jeff King <peff@peff.net>
Subject: ab/fsck-unexpected-type (and "cat-file replace handling and optimization")
Date: Tue, 05 Oct 2021 22:47:26 +0200 [thread overview]
Message-ID: <87bl43jit5.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqo884tkxd.fsf@gitster.g>
On Mon, Oct 04 2021, Junio C Hamano wrote:
> * ab/fsck-unexpected-type (2021-10-01) 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 think it's ready, also noted last time around[1]. You had one question
on the v10, which I hope I answered to your satisfaction at[2].
Note that Jeff's just-submitted cat-file series[3] will conflict with
this, as they both adjust the same "garbage" object tests. The semantic
conflict is minimal/none, but the textual one is probably annoying
(e.g. his 1/5 uses a variable I split/renamed).
Jeff: Depending on what Junio thinks of queuing ab/fsck-unexpected-type
for next what do you think about rebasing your series on top, or perhaps
take a look at the v10[4] of it/ack it in case that helps with that (since
you've been looking at some related code just now...).
1. https://lore.kernel.org/git/87y27dq70e.fsf@evledraar.gmail.com/
2. https://lore.kernel.org/git/87sfxkpdqp.fsf@evledraar.gmail.com/
3. https://lore.kernel.org/git/YVy1sx8Xb1xMLFQT@coredump.intra.peff.net/
4. https://lore.kernel.org/git/cover-v10-00.17-00000000000-20211001T091051Z-avarab@gmail.com/
next prev parent reply other threads:[~2021-10-05 20:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 23:44 What's cooking in git.git (Oct 2021, #01; Mon, 4) Junio C Hamano
2021-10-04 23:52 ` Taylor Blau
2021-10-05 16:01 ` ab/refs-errno-cleanup Ævar Arnfjörð Bjarmason
2021-10-05 16:47 ` hm/paint-hits-in-log-grep Ævar Arnfjörð Bjarmason
2021-10-05 17:07 ` ab/designated-initializers-more Ævar Arnfjörð Bjarmason
2021-10-05 20:47 ` Ævar Arnfjörð Bjarmason [this message]
2021-10-05 22:01 ` ab/fsck-unexpected-type (and "cat-file replace handling and optimization") Jeff King
2021-10-06 8:54 ` Ævar Arnfjörð Bjarmason
2021-10-07 21:37 ` Junio C Hamano
2021-10-08 2:25 ` Jeff King
2021-10-08 20:50 ` Junio C Hamano
2021-10-06 10:14 ` ab/make-sparse-for-real Ævar Arnfjörð Bjarmason
2021-10-06 10:17 ` ab/parse-options-cleanup & ab/align-parse-options-help & ab/help-config-vars Ævar Arnfjörð Bjarmason
2021-10-06 16:44 ` Junio C Hamano
2021-10-06 10:26 ` ab/refs-errno-cleanup & "errno" removal in the refs backend Æ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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bl43jit5.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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.
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 NNTP newsgroup(s).