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

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

[Hussain Sitamouwala]

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

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

[Junio C Hamano]

Hussain Sitamouwala <husainsitamuwala21@gmail.com> writes:

> Document that accepted promisor remotes are tried before other promisor remotes, and that Git falls back to the next remote when a fetch fails.

Hussain, the above line is overly long.  Usual line-length
limitation rules for this mailing list applies (~70 columns).

Hussain, where did this documentation update come from?  What
prompted you to make this update?  Is this documenting a
long-standing existing behaviour?  Is this trying to fill
documentation gap left by more recent behaviour change?  Something
else?

Christian, does the behaviour this patch documents the current one?
How does it relate to 8808e61fd3 (promisor-remote: try accepted
remotes before others in get_direct(), 2026-04-07) which you did?

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.

Thanks.

> 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: