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

Re: [PATCH] partial-clone: document promisor remote fetch ordering

From
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Date
Nov 13, 2026, 13:53 UTC
Message-ID
<1c124d5d-790b-4d22-af22-c53573e6d2ec@gmail.com>
In-Reply-To
<xmqq5wy89rq6.fsf@gitster.g>
On 11/8/26 04:25, Junio C Hamano wrote:
Show 9 quoted lines
> Hussain Sitamouwala <husainsitamuwala21@gmail.com> writes:
>  > It seems there are multiple people sending messages with words like
> "promisor", "fetch", "order", and "Outreachy" on their "Subject:"
> fairly recently, but are you in charge of herding these folks, or is
> somebody else helping them?  Without knowing if there is somebody
> central coordinating these that I can ask about, it is hard to tell
> if these people are making coherent effort to achieve something
> worthwhile, or if they are just randomly banging the door.
> The patches surrounding promisor-remote are coming through because we had proposed the following project for this year's Outreachy round.
  Implement promisor remote fetch ordering
  When a Git repository is configured with multiple promisor remotes,
  there’s currently no mechanism to specify or optimize the order in
  which these remotes should be queried when fetching missing objects.
  Different remotes may have different performance characteristics,
  costs, or reliability, making fetch order an important consideration.
  This project aims to implement a fetch ordering mechanism for multiple
  promisor remotes. The order could be:
    - Configured locally by the client
    - Advertised by servers through the promisor-remote protocol
  The key challenge is designing a flexible system that allows servers
  to communicate their preferred fetch order to clients (to ensure
  optimal performance and cost management).
See also: https://lore.kernel.org/git/CAP8UFD3kd=6QHp2oB+t+g-2D8bY-Oe5+_Vk+RJeaCa_xhxGrsA@mail.gmail.com/
I have volunteered to mentor the same and Chrisitian has mentioned that he'll help with the project. Feel free to ping me too in case you see anything around this you need some help with.
Sorry for the late response. I just thought I'll fill in with the context in case it helps.
-- 
Sivaraam
Previous: Junio C HamanoNext: Hussain Sitamouwala
Message 3 of 7 in “partial-clone: document promisor remote fetch ordering”
  1. partial-clone: document promisor remote fetch orderingHussain Sitamouwala, Nov 7, 2026
  2. Junio C HamanoNov 7, 2026
  3. Kaartic SivaraamNov 13, 2026
  4. Hussain SitamouwalaNov 13, 2026
  5. Hussain SitamouwalaNov 13, 2026
  6. Kaartic SivaraamNov 14, 2026
  7. Kaartic SivaraamNov 14, 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.