Re: [PATCH v10 1/5] fetch: add remote.<name>.refmap
On 25/10/2026 22:15, Junio C Hamano wrote:
Show 8 quoted lines
> > I just encountered a case where I wished to configure both refmap
> and fetch at the same time. From a second remote (let's call it
> "cabal"), store any branch fetched from them in refs/remotes/cabal/
> but I want to fetch only their 'master', 'next' and 'seen'. I'd
> want to be able to write something like:
> > [remote "cabal"]
> fetch = master next seen
> refmap = +refs/heads/*:refs/remotes/cabal/*
That's a coincidence, I sent a message earlier [1] arguing that we should have separate config settings for "what to fetch" and "where to store it"
Thanks
Phillip
[1] https://lore.kernel.org/git/e6af5d1e-4ca1-48a5-8a84-5e0cefbdbc2b@gmail.com
> > And, no, this does not require any inferring based on what is
> checked out and what the checked out branch tracks.