{"thread":{"id":"66608","subject":"[Outreachy] Promisor remote fetch ordering: clarifying the current behavior","startedAt":"2026-10-20T22:06:06Z","lastAt":"2026-10-20T22:06:06Z","messageCount":1,"participants":["Wasswa Edson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"555629","messageId":"CA+ew3JvT6miEzLBVoBeR7eQMYHWzF=9Y7MFZBBnF2gXkf5Tsow@mail.gmail.com","threadId":"66608","inReplyTo":null,"subject":"[Outreachy] Promisor remote fetch ordering: clarifying the current behavior","fromName":"Wasswa Edson","fromEmail":"edsonwasswa54@gmail.com","sentAt":"2026-10-20T22:06:06Z","receivedAt":"2026-10-20T22:06:06Z","isPatch":false,"sender":{"key":"edsonwasswa54@gmail.com","avatar":null},"body":"I’ve been going through the existing implementation and documentation\nfor the Implement promisor remote fetch ordering project to understand\nhow things currently work before deciding what to contribute.\nFrom what I’ve found, Documentation/technical/partial-clone.adoc\nalready describes the ordering of configured promisor remotes, while\nDocumentation/gitprotocol-v2.adoc explains that server-accepted\nremotes are tried first. The corresponding logic is also present in\npromisor-remote.c.\nThis made me wonder whether the main goal is to introduce a new way of\ncontrolling the order, rather than document the current behavior. I’d\nlike to avoid submitting a change that simply repeats what is already\ndocumented or implemented.\nCould you help me understand the specific limitation this project is\nintended to address, or point me toward the part of the implementation\nwhere a contribution would be most useful?\nI’d appreciate the guidance. I’m keen to understand the problem\nproperly and make a contribution that genuinely improves Git.\nBest regards,\nEdson\n\n"}]}