`git fetch <remote> <refspec>…` <refspec (without dst)>s are mapped by other <refspec (with dst)> resulting in extra remote tracking branches

Han Jiang· Sep 5, 2024, 04:38 UTC · lore

Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)

cd '/'; cd '/'; rm --force --recursive -- './test_git2'; mkdir "$_"; cd "$_"; mkdir --parents -- './server' './client';

git -C './server' init --bare './repo.git'

git -C './client' init './repo' git -C './client/repo' remote add server 'file://'"$(realpath './server/repo.git')" git -C './client/repo' config set --local 'remote.server.fetch' '+refs/heads/*:refs/remotes/server/*2' git -C './client/repo' remote --verbose git -C './client/repo' config list --local --show-scope --show-origin

git --git-dir='./server/repo.git' --work-tree='.' commit --allow-empty -m "$((++number))"; git -C './server/repo.git' branch --force branch1; git -C './server/repo.git' branch --force branch2 git -C './client/repo' fetch server '+refs/heads/branch*:refs/remotes/server/branch*3' '+refs/heads/branch*:refs/remotes/server/branch*4' git -C './client/repo' log --all

git --git-dir='./server/repo.git' --work-tree='.' commit --allow-empty -m "$((++number))"; git -C './server/repo.git' branch --force branch1; git -C './server/repo.git' branch --force branch2 git -C './client/repo' fetch server --refmap='+refs/heads/*:refs/remotes/server/*5' --refmap='+refs/heads/*:refs/remotes/server/*6' 'branch1' git -C './client/repo' log --all

git --git-dir='./server/repo.git' --work-tree='.' commit --allow-empty -m "$((++number))"; git -C './server/repo.git' branch --force branch1; git -C './server/repo.git' branch --force branch2 git -C './client/repo' fetch server --refmap='+refs/heads/*:refs/remotes/server/*5' --refmap='+refs/heads/*:refs/remotes/server/*6' '+refs/heads/branch*:refs/remotes/server/branch*7' git -C './client/repo' log --all

git --git-dir='./server/repo.git' --work-tree='.' commit --allow-empty -m "$((++number))"; git -C './server/repo.git' branch --force branch1; git -C './server/repo.git' branch --force branch2 git -C './client/repo' fetch server --refmap='+refs/heads/*:refs/remotes/server/*5' --refmap='+refs/heads/*:refs/remotes/server/*6' '+refs/heads/branch*:refs/remotes/server/branch*7' '+refs/heads/branch*:refs/remotes/server/branch*8' 'branch1' git -C './client/repo' log --all

What did you expect to happen? (Expected behavior)

`git fetch server '+refs/heads/branch*:refs/remotes/server/branch*3' '+refs/heads/branch*:refs/remotes/server/branch*4' 'branch1'` results in: server/branch13 server/branch23 server/branch14 server/branch24 server/branch12

`git fetch server --refmap='+refs/heads/*:refs/remotes/server/*5' --refmap='+refs/heads/*:refs/remotes/server/*6' '+refs/heads/branch*:refs/remotes/server/branch*7' '+refs/heads/branch*:refs/remotes/server/branch*8' 'branch1'` results in: server/branch17 server/branch27 server/branch18 server/branch28 server/branch15 server/branch16 or: server/branch17 server/branch27 server/branch18 server/branch28 server/branch12 server/branch15 server/branch16

What happened instead? (Actual behavior)

What's different between what you expected and what actually happened?

Anything else you want to add:

Please review the rest of the bug report below. You can delete any lines you don't wish to share.

[System Info]
git version:
git version 2.46.0.windows.1
cpu: x86_64
built from commit: 2e6a859ffc0471f60f79c1256f766042b0d5d17d
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
feature: fsmonitor--daemon
libcurl: 8.9.0
OpenSSL: OpenSSL 3.2.2 4 Jun 2024
zlib: 1.3.1
uname: Windows 10.0 22631
compiler info: gnuc: 14.1
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe

[Enabled Hooks] not run from a git repository - no hooks to show