From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH v3 4/4] connected: search promisor objects generically
Date: Thu, 25 Jun 2026 13:22:02 -0700 [thread overview]
Message-ID: <xmqq4iiqfk0l.fsf@gitster.g> (raw)
In-Reply-To: <20260625-pks-connected-generic-promisor-checks-v3-4-7308f3b9dc44@pks.im> (Patrick Steinhardt's message of "Thu, 25 Jun 2026 11:57:42 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> When performing connectivity checks we have to figure out whether any of
> the new objects are promisor objects, as we cannot assume full
> connectivity if so.
>
> This check is performed by iterating through all packfiles in the
> repository and searching each of them for the given object. Of course,
> this mechanism is quite specific to implementation details of the object
> database, as we assume that it uses packfiles in the first place.
>
> Refactor the logic so that we instead use `odb_for_each_object_ext()`
> with an object prefix filter and the `ODB_FOR_EACH_OBJECT_PROMISOR_ONLY`
> flag. This will yield all objects that have the exact object name and
> that are part of a promisor pack in a generic way.
>
> Add a test to verify that we indeed use the optimization.
OK. The new test is a good way to catch the issue we noticed in the
previous round, I guess. Looking good.
Thanks.
next prev parent reply other threads:[~2026-06-25 20:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 8:49 [PATCH 0/3] connected: search promisor objects generically Patrick Steinhardt
2026-06-22 8:49 ` [PATCH 1/3] odb/source-packed: extract logic to skip certain packs Patrick Steinhardt
2026-06-22 17:51 ` Junio C Hamano
2026-06-22 8:49 ` [PATCH 2/3] odb/source-packed: support flags when iterating an object prefix Patrick Steinhardt
2026-06-22 8:49 ` [PATCH 3/3] connected: search promisor objects generically Patrick Steinhardt
2026-06-22 17:57 ` Junio C Hamano
2026-06-24 9:33 ` Patrick Steinhardt
2026-06-23 7:45 ` Christian Couder
2026-06-24 9:33 ` Patrick Steinhardt
2026-06-24 10:37 ` [PATCH v2 0/4] " Patrick Steinhardt
2026-06-24 10:37 ` [PATCH v2 1/4] odb/source-packed: extract logic to skip certain packs Patrick Steinhardt
2026-06-24 10:37 ` [PATCH v2 2/4] odb/source-packed: support flags when iterating an object prefix Patrick Steinhardt
2026-06-24 17:02 ` Christian Couder
2026-06-25 5:52 ` Patrick Steinhardt
2026-06-24 10:37 ` [PATCH v2 3/4] connected: split out promisor-based connectivity check Patrick Steinhardt
2026-06-24 10:37 ` [PATCH v2 4/4] connected: search promisor objects generically Patrick Steinhardt
2026-06-24 16:27 ` Junio C Hamano
2026-06-25 5:54 ` Patrick Steinhardt
2026-06-25 9:57 ` [PATCH v3 0/4] " Patrick Steinhardt
2026-06-25 9:57 ` [PATCH v3 1/4] odb/source-packed: extract logic to skip certain packs Patrick Steinhardt
2026-06-25 9:57 ` [PATCH v3 2/4] odb/source-packed: support flags when iterating an object prefix Patrick Steinhardt
2026-06-25 9:57 ` [PATCH v3 3/4] connected: split out promisor-based connectivity check Patrick Steinhardt
2026-06-25 9:57 ` [PATCH v3 4/4] connected: search promisor objects generically Patrick Steinhardt
2026-06-25 20:22 ` Junio C Hamano [this message]
2026-06-26 6:55 ` Christian Couder
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=xmqq4iiqfk0l.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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.