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 10, 2026, 12:58 UTC
Message-ID
<CANRKfoDaaF+Dp8b_7GvXsH9mGWqHSxDWK9HbxCcc_j=gz+V=Tg@mail.gmail.com>
In-Reply-To
<xmqqcxse101u.fsf@gitster.g>
On Mon, Nov 9, 2026 at 9:15 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Was that extra "not wrong per-se but totally unnecessary without
> adding any new information" sentence added by LLM by any chance?
> Just being curious.

No, I wrote that sentence myself. I was trying to spell out the fallback behavior explicitly, but you are right that "tried one after the other" already covers it.

I do use an AI tool to clear up doubts while I am learning the codebase, but I did not use it to generate the patch text.

Thanks for queueing v3.

Thanks, Hussain

Previous: Junio C HamanoNext: Hussain Sitamouwala
Message 9 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.