From: Phillip Wood Date: Tue, 17 Nov 2026 11:08:36 GMT Subject: Re: [PATCH v13 0/6] fetch: avoid fetching every branch of a new remote in a shallow repo Message-ID: <1276fcfe-9f2c-4a2c-ade9-b88f33ae5d84@gmail.com> In-Reply-To: Hi Matt On 12/11/2026 15:25, Matt Hunter wrote: > On Thu Nov 12, 2026 at 6:16 AM EST, Phillip Wood wrote: >> 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. > > > > 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. Thanks for the link. For this topic we're still waiting for a response to this part of [1] from three weeks ago > For now, as this "what is tracked by the local branches" is the only > kind of smart that was designed to decide what to fetch, it may be OK > to use "you gave me nothing to specify what to fetch, so I'll guess > using the smart". But when we introduce more kinds of smart later, > this becomes a problem. So I do agree with you that we should have > something to specifically say "when I do not explicitly give you > what to fetch, decide based on what local branches track". so perhaps we should give that other topic priority while we wait. Thanks Phillip [1] https://lore.kernel.org/git/xmqqh5i8tqjx.fsf@gitster.g/