Re: [PATCH v10 1/5] fetch: add remote.<name>.refmap

[Phillip Wood <phillip.wood123@gmail.com>]

On 26/10/2026 15:48, Junio C Hamano wrote:
> 
> I actually do not think we should have master next seen on the same
> remote.cabal.fetch configuration variable.  It is a multi-valued
> variable, so it should read more like
> 
>           [remote "cabal"]
>                   fetch = refs/heads/master
>                   fetch = refs/heads/next
>                   fetch = refs/heads/seen
>                   refmap = +refs/heads/*:refs/remotes/cabal/*

Doesn't that cause older versions of git to try and update the local 
branch when fetching, or is it only when pushing that we'll fill in the 
right hand side of the refspec with a copy of the left hand side? If we 
use a different config setting for "what to fetch" then users that want 
the new behavior can unset remote.<name>.fetch and older versions of git 
will fail rather than overwriting local branches when there is no 
refspec on the commandline.

Thanks

Phillip

> 
> And without these remote.cabal.fetch configured, but with
> remote.cabal.refmap configured, this command line
> 
> 	$ git fetch cabal next
> 
> should work just like
> 
> 	$ git fetch cabal \
> 		--refmap="+refs/heads/*:refs/remotes/cabal/*" \
> 		next
> 
> I think.
> 
> Thanks.