Explain that promisor remotes accepted from a server are tried
before other promisor remotes. The ordering was introduced by
8808e61fd3 (promisor-remote: try accepted remotes before others in
get_direct(), 2026-04-07).
Signed-off-by: Hussain Sitamouwala <redacted>
---
Changes since v2:
- removed the redundant fetch-fallback sentence, as suggested by Junio
- dropped the matching clause from the commit message
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..52fce44384 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 that the
+client accepted from a server's advertisement are tried before the
+other promisor remotes.
Remotes that are considered "promisor" remotes are those specified by
the following configuration variables:
--
2.53.0