From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Derrick Stolee <derrickstolee@github.com>
Subject: Re: [PATCH] pack-bitmap.c: gracefully degrade on failure to load MIDX'd pack
Date: Mon, 12 Jun 2023 14:19:01 -0700 [thread overview]
Message-ID: <xmqqpm608jlm.fsf@gitster.g> (raw)
In-Reply-To: <f123b68cb8a277fbf105b1789a84b9405a499b79.1686178854.git.me@ttaylorr.com> (Taylor Blau's message of "Wed, 7 Jun 2023 19:01:00 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> When opening a MIDX bitmap, we the pack-bitmap machinery eagerly calls
I guess s/we // is needed here?
> When opening one of these packs fails, the pack-bitmap code will `die()`
> indicating that it can't open one of the packs in the MIDX. This
> indicates that the MIDX is somehow broken with respect to the current
> state of the repository. When this is the case, we indeed cannot make
> use of the MIDX bitmap to speed up reachability traversals.
>
> However, it does not mean that we can't perform reachability traversals
> at all. In other failure modes, that same function calls `warning()` and
> then returns -1, indicating to its caller (`open_bitmap()`) that we
> should either look for a pack bitmap if one is available, or perform
> normal object traversal without using bitmaps at all.
Makes sense.
prev parent reply other threads:[~2023-06-12 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 23:01 [PATCH] pack-bitmap.c: gracefully degrade on failure to load MIDX'd pack Taylor Blau
2023-06-12 21:19 ` Junio C Hamano [this message]
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=xmqqpm608jlm.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.