git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
WEWasswa Edson <edsonwasswa54@gmail.com>
Date
Oct 20, 2026, 22:06 UTC
Message-ID
<CA+ew3JvT6miEzLBVoBeR7eQMYHWzF=9Y7MFZBBnF2gXkf5Tsow@mail.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

Message 1 of 1 in “[Outreachy] Promisor remote fetch ordering: clarifying the current behavior”
  1. Wasswa EdsonOct 20, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.