Re: [PATCH 7/9] list-objects-filter-options: implement auto filter resolution
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Feb 12, 2026, 10:07 UTC
- Message-ID
- <CAP8UFD04BTTjXhTz_6HbSZiWZC77k0XfnusaP+V9h_3bzH9=+w@mail.gmail.com>
- In-Reply-To
- <aYxsgL3uMpNlLe8o@pks.im>
On Wed, Feb 11, 2026 at 12:48 PM Patrick Steinhardt <ps@pks.im> wrote:
Show 6 quoted lines
> One thought I recently had: if one selects multiple promisor remotes, > how does the client know which promisor remote to fetch a certain object > from? We don't always have enough information about a missing object to > be able to tell which of the filters would have excluded it, so it's not > possible to basically "reverse" the filtering and deduce from them which > remote should have them.
When there are multiple promisor remotes, the client will try to fetch the missing objects from the promisor remotes in the order they appear in the config file, then it will try the "main remote" if it still couldn't fetch some objects.
Note that this isn't changed by this patch series. This is how it works since it has been possible to configure multiple promisor remotes. It's also documented in the "Using many promisor remotes" of "Documentation/technical/partial-clone.adoc".
By the way the doc says "the long term plan should be to make the order somehow fully configurable" and this is what the "Implement promisor remote fetch ordering" GSoC 2026 project is about. See:
https://git.github.io/SoC-2026-Ideas/
(Thanks to Kaartic Sivaraam who recently submitted the PR to add this and other projects to that page.)