Re: [Outreachy][PATCH v2] promisor-remote: honor promisor.fetchOrder when trying remotes
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Nov 13, 2026, 17:10 UTC
- Message-ID
- <CAP8UFD0zMp-e3Fp5SjXuHiu25718=vf+qetzwpRZmBPMJ8Vb0Q@mail.gmail.com>
- In-Reply-To
- <xmqq8q36q3il.fsf@gitster.g>
On Fri, Nov 6, 2026 at 12:09 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 5 quoted lines
> > Christian, I thought you are the go-to person for promisor remote, > and if I am not mistaken, you worked on letting the server side tell > the clients which promisors to use first? How would this mesh well > with that?
Sorry, for the late reply. I didn't have much time this week.
First in https://git.github.io/General-Microproject-Information/ we have a "Don’t work on a proposed project right away" section, but unfortunately this patch is addressing the main issue of a project we are proposing.
In general I think that there should be a design doc or a long discussion before we start implementing something, because the problem could be complex. When you are fetching from different remotes, remote A might want the client to get some objects from a set of promisor remotes, like A1 and A2, while remote B, might advertise others like B1, B2 and B3. Also after a few regular fetches from let's say A and B, the client might need to lazy fetch some objects. Then it's not clear which order would be best. A single order might not work well. The best order might depend on the remote from which related objects were fetched.