# [Outreachy] Promisor remote fetch ordering: clarifying the current behavior

1 messages from 2026-10-20 to 2026-10-20. Participants: Wasswa Edson.
Thread: https://gitlist.dev/t/66608

## Wasswa Edson, 2026-10-20 22:06

Subject: [Outreachy] Promisor remote fetch ordering: clarifying the current behavior
Message-ID: <CA+ew3JvT6miEzLBVoBeR7eQMYHWzF=9Y7MFZBBnF2gXkf5Tsow@mail.gmail.com>
URL: https://gitlist.dev/e/CA%2Bew3JvT6miEzLBVoBeR7eQMYHWzF%3D9Y7MFZBBnF2gXkf5Tsow%40mail.gmail.com

```
I’ve been going through the existing implementation and documentation
for the Implement promisor remote fetch ordering project to understand
how things currently work before deciding what to contribute.
From what I’ve found, Documentation/technical/partial-clone.adoc
already describes the ordering of configured promisor remotes, while
Documentation/gitprotocol-v2.adoc explains that server-accepted
remotes are tried first. The corresponding logic is also present in
promisor-remote.c.
This made me wonder whether the main goal is to introduce a new way of
controlling the order, rather than document the current behavior. I’d
like to avoid submitting a change that simply repeats what is already
documented or implemented.
Could you help me understand the specific limitation this project is
intended to address, or point me toward the part of the implementation
where a contribution would be most useful?
I’d appreciate the guidance. I’m keen to understand the problem
properly and make a contribution that genuinely improves Git.
Best regards,
Edson


```
