From: Junio C Hamano Date: Wed, 14 Oct 2026 19:07:42 GMT Subject: Re: [RFC] pull: custom fetch refspecs and fork-point lookup Message-ID: In-Reply-To: jyotish kumar writes: > While reading `builtin/pull.c`, I came across a FIXME in > `get_tracking_branch()` concerning the assumption that remote branches > follow the default mapping from `refs/heads/` to > `refs/remotes//`. > ... > Does this analysis sound correct? I would appreciate feedback on > whether this is a real issue and whether resolving the configured > fetch mapping would be the right direction to address it. The reason the "FIXME" you noticed exists is that the assumption the code makes is broken. Assuming that refs/remotes// tracks from would break when a customized fetch refspec is used. I vaguely recall mentioning a similar "map between a remote-tracking branch and a branch at the remote" issue while discussing a recent work by Harald to narrow a "git fetch" that does not specify what to fetch, but I cannot find a mailing list archive reference, sorry.