Re: [PATCH v13 0/6] fetch: avoid fetching every branch of a new remote in a shallow repo
- From
Matt Hunter <m@lfurio.us>
- Date
- Nov 12, 2026, 15:25 UTC
- Message-ID
- <DMTC5DR3ROPP.5V7HNV9ERYFT@lfurio.us>
- In-Reply-To
- <5566b994-1070-41d3-807b-5fac9ddaa3d8@gmail.com>
On Thu Nov 12, 2026 at 6:16 AM EST, Phillip Wood wrote:
Show 9 quoted lines
> On 11/11/2026 17:37, Junio C Hamano wrote: > >> In any case, this topic one is keeping a topic by another author >> waiting to settle, so we have stronger incentive to see it move past >> the finish line. > > What topic is that? - I can't see anything marked as depending on this > in the latest "what's cooking" email. Would merging the first part of > this series unblock the other one?
I believe that is ch/remote-defer-follow-remote-head-validation, which doesn't strictly depend on the changes from this topic, but the two have textual conflicts that the other author is deferring to resolve when this one lands.
<CAHeTm9M5maWM=yrJPNzCibv_rewH3-yBK8J5-MDyDvPzfihe4A@mail.gmail.com>
It looks like if this topic were merged up to patch 3/6 (fetch: infer branches to fetch from a refmap-only remote), the situation could resolve.