Re: [PATCH v6 0/4] fetch: avoid fetching every branch of a new remote in a shallow repo

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 5, 2026, 12:17 UTC
Message-ID: <xmqqv77gnxyg.fsf@gitster.g>
In-Reply-To: <CAHwyqnXz+acRBytu9tWL+RzsKnzTZyZCnzzQQhEFjvWT5cgoww@mail.gmail.com>

Harald Nordgren <haraldnordgren@gmail.com> writes:

Show 8 quoted lines

>> If you try to run this with [1/4] alone, however, it errors out with
>> "fatal: --refmap option is only meaningful with command-line
>> refspec", which is suboptimal when triggered by a configuration
>> variable.  Even though our design says that remote.*.refmap makes
>> the command behave as if the user gave '--refmap' on the command
>> line, applying that rule here is a bit too strict.
>
> Thanks for pointing that out. How did you find that?

By thinking the process through while writing these very basic tests.

I think this topic textually interacts with Collin's followRemoteHAD work. I tried to be careful while resolving the conflicts when I merged both to 'seen', but please double check the result when I push it out.