Re: SIGSEGV Error Occurs When Attempting to Unbundle Without Initializing Git Repository.

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 12, 2024, 15:55 UTC
Message-ID: <xmqq1q2t7n33.fsf@gitster.g>
In-Reply-To: <20240812114733.GA3732689@coredump.intra.peff.net>

Jeff King <peff@peff.net> writes:

>   - "verify" requires a repo, which I wouldn't have expected, but I
>     guess it's because we probably unbundle under the hood to walk.
>     Anyway, it gets the ordering right here and checks the repo before
>     opening the bundle.

In hindsight "verify" is misnamed and overrated. Its purpose is to check if the bundle can be unbundled into your _current_ repository by checking if you have all the commits _required_ to unbundle the bundle.

In fact, I doubt that "verify" looks at the pack stream part of the file at all.

>   - list-heads doesn't require a repo, and segfaults. So it really does
>     need some kind of detection or default to know which hash to use.

Yes.