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

Re: [PATCH v2] doc: describe promisor remote fetch order

From
HSHussain Sitamouwala <husainsitamuwala21@gmail.com>
Date
Nov 8, 2026, 19:12 UTC
Message-ID
<20261108191212.594-1-husainsitamuwala21@gmail.com>
In-Reply-To
<xmqqse1b2ljp.fsf@gitster.g>
Hi Junio,
Thanks for the review.
> Would it mean the same thing if we replace "next remote" with
> "other promisor remotes"?

Yes, that is what I meant. When a fetch from one promisor remote fails, the objects that are still missing are requested from the other promisor remotes, in turn. "Other promisor remotes" is clearer, and it matches the previous sentence, so I will change both places in the next version.

Thanks, Hussain

Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 12 in “doc: describe promisor remote fetch order”
  1. doc: describe promisor remote fetch orderHussain Sitamouwala, Nov 8, 2026
  2. Junio C HamanoNov 8, 2026
  3. Hussain SitamouwalaNov 8, 2026
  4. Junio C HamanoNov 8, 2026
  5. Hussain SitamouwalaNov 8, 2026
  6. Junio C HamanoNov 8, 2026
  7. Hussain SitamouwalaNov 8, 2026
  8. Junio C HamanoNov 9, 2026
  9. Hussain SitamouwalaNov 10, 2026
  10. environment: move assume_unchanged into repo_config_valuesHussain Sitamouwala, Nov 8, 2026
  11. doc: describe promisor remote fetch orderHussain Sitamouwala, Nov 8, 2026
  12. Junio C HamanoNov 9, 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.