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

Re: [PATCH v3] promisor-remote: prevent lazy-fetch recursion in child fetch

From
PTPaul Tarjan <paul@paultarjan.com>
Date
Apr 17, 2026, 02:21 UTC
Message-ID
<20260417022146.57388-1-github@paulisageek.com>
In-Reply-To
<xmqqse6p0cvm.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> So, is this topic still viable?

Yes, still viable from my end. The patch fixed the production problem I ran into.

I thought v3 had addressed the outstanding feedback (HTTP behavioral test, dropped the commit-graph comparison, packet trace and pack-reuse analysis sent on Mar 13 in response to Peff's questions), but I may have missed something. Is there a specific concern I should address?

Paul
Message 1 of 1 in “Re: [PATCH v3] promisor-remote: prevent lazy-fetch recursion in child fetch”
  1. Paul TarjanApr 17, 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.