{"thread":{"id":"65504","subject":"Re: [PATCH v3] promisor-remote: prevent lazy-fetch recursion in child fetch","startedAt":"2026-04-17T02:21:49Z","lastAt":"2026-04-17T02:21:49Z","messageCount":1,"participants":["Paul Tarjan"],"isPatch":true,"patchVersion":3,"patchTotal":null},"messages":[{"id":"541805","messageId":"20260417022146.57388-1-github@paulisageek.com","threadId":"65504","inReplyTo":"xmqqse6p0cvm.fsf@gitster.g","subject":"Re: [PATCH v3] promisor-remote: prevent lazy-fetch recursion in child fetch","fromName":"Paul Tarjan","fromEmail":"paul@paultarjan.com","sentAt":"2026-04-17T02:21:46Z","receivedAt":"2026-04-17T02:21:49Z","isPatch":true,"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n> So, is this topic still viable?\n\nYes, still viable from my end. The patch fixed the production\nproblem I ran into.\n\nI thought v3 had addressed the outstanding feedback (HTTP\nbehavioral test, dropped the commit-graph comparison, packet\ntrace and pack-reuse analysis sent on Mar 13 in response to\nPeff's questions), but I may have missed something. Is there a\nspecific concern I should address?\n\nPaul\n"}]}