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

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

From
HSHussain Sitamouwala <husainsitamuwala21@gmail.com>
Date
Nov 7, 2026, 15:04 UTC
Message-ID
<20261107150433.17540-1-husainsitamuwala21@gmail.com>
Document that accepted promisor remotes are tried before other promisor remotes, and that Git falls back to the next remote when a fetch fails.
Signed-off-by: Hussain Sitamouwala <husainsitamuwala21@gmail.com>
---
 Documentation/technical/partial-clone.adoc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/technical/partial-clone.adoc b/Documentation/technical/partial-clone.adoc
index 18718a3840..9720b856ce 100644
--- a/Documentation/technical/partial-clone.adoc
+++ b/Documentation/technical/partial-clone.adoc
@@ -195,7 +195,9 @@ cache servers for fetching missing blobs while continuing to do
 filtered `git-fetch` commands from the central server.
 
 When fetching objects, promisor remotes are tried one after the other
-until all the objects have been fetched.
+until all the objects have been fetched. Promisor remotes accepted from a
+server are tried before other promisor remotes. If a fetch from a remote fails,
+Git tries the remaining objects from the next remote.
 
 Remotes that are considered "promisor" remotes are those specified by
 the following configuration variables:
-- 
2.53.0
Next: Junio C Hamano
Message 1 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.