From: Junio C Hamano Date: Tue, 17 Nov 2026 21:06:17 GMT Subject: Re: [PATCH v14 1/5] fetch: add remote..fetchRefmap Message-ID: In-Reply-To: Phillip Wood writes: >> I can buy it if the suggestion was to allow passing --no-refmap from >> the command line (or would --refmap="" work?) to ignore .fetchRefmap >> configuration, though. > > I think --refmap="" might work as --refmap overrides the config and > --refmap="" is the documented way to ignore the ".fetch" config. Do you mean ... ignore the .fetchRefmap config (not ".fetch", which is used as the default for refspecs and not value to a dashed option)? All that said, it feels much more flexible if a refspec with a destination (whether on the command line or in the configuration) simply ignores the refmap. In other words, the refmap would only apply to refspec entries that lack a destination, leaving elements with their own destination untouched. This way, we won't have to worry about what --refmap="" means. So I'm completely fine with going in that direction. The only thing I care about is keeping a clear one-to-one relationship between the configuration and the command-line option: the configuration sets the default, and the command-line option overrides it. Thanks.