From: Paul Tarjan <paul@paultarjan.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, ps@pks.im, peff@peff.net,
gitgitgadget@gmail.com, christian.couder@gmail.com,
hanxin.hx@bytedance.com
Subject: Re: [PATCH v3] promisor-remote: prevent lazy-fetch recursion in child fetch
Date: Thu, 16 Apr 2026 20:21:46 -0600 [thread overview]
Message-ID: <20260417022146.57388-1-github@paulisageek.com> (raw)
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
next parent reply other threads:[~2026-04-17 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xmqqse6p0cvm.fsf@gitster.g>
2026-04-17 2:21 ` Paul Tarjan [this message]
2026-03-13 1:43 [PATCH v2] promisor-remote: prevent lazy-fetch recursion in child fetch Jeff King
2026-03-13 12:43 ` [PATCH v3] " Paul Tarjan
-- strict thread matches above, loose matches on Subject: below --
2026-03-12 7:27 [PATCH v2] " Patrick Steinhardt
2026-03-13 12:43 ` [PATCH v3] " Paul Tarjan
2026-04-15 18:05 ` Junio C Hamano
2026-03-04 18:27 [PATCH v2] " Paul Tarjan via GitGitGadget
2026-03-11 14:19 ` [PATCH v3] " Paul Tarjan via GitGitGadget
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260417022146.57388-1-github@paulisageek.com \
--to=paul@paultarjan.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=hanxin.hx@bytedance.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.