From: Han Jiang <jhcarl0814@gmail.com>
To: git@vger.kernel.org
Subject: `git remote prune <remote>…` (equivalent to git fetch --prune <remote> except that no new references will be fetched) ignores `fetch.pruneTags` (and `git fetch --dry-run` prints same tag twice)
Date: Wed, 4 Sep 2024 12:08:19 +1200 [thread overview]
Message-ID: <CANrWfmR1nTDF-ts3n2PpH2C+uvBzDm7ZEXh0StuwPZRmm80T1A@mail.gmail.com> (raw)
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_git'; mkdir "$_"; cd "$_";
mkdir --parents -- './server' './client';
git -C './server' init --bare './repo.git'
git --git-dir='./server/repo.git' --work-tree='.' commit --allow-empty
-m "$((++number))"
git -C './server/repo.git' branch branch1; git -C './server/repo.git'
branch branch2; git -C './server/repo.git' tag tag1; git -C
'./server/repo.git' tag tag2
git -C './client' init './repo'
git -C './client/repo' remote add server 'file://'"$(realpath
'./server/repo.git')"
git -C './client/repo' remote --verbose
git -C './client/repo' config list --local --show-scope --show-origin
git -C './client/repo' branch --list --all --verbose --verbose
git -C './client/repo' tag --list
git -C './client/repo' fetch --all
git -C './client/repo' branch --list --all --verbose --verbose
git -C './client/repo' tag --list
git -C './server/repo.git' branch --delete branch1; git -C
'./server/repo.git' branch branch3; git -C './server/repo.git' tag
--delete tag1; git -C './server/repo.git' tag tag3
git -C './client/repo' remote prune --dry-run server
git -C './client/repo' fetch --prune --dry-run server
git -C './client/repo' config set --local 'fetch.pruneTags' 'true'
git -C './client/repo' remote prune --dry-run server
git -C './client/repo' fetch --prune --dry-run server
git -C './client/repo' config unset --local 'fetch.pruneTags'
git -C './client/repo' config set --local --append
'remote.server.fetch' '+refs/tags/*:refs/tags/*'
git -C './client/repo' remote prune --dry-run server
git -C './client/repo' fetch --prune --dry-run server
git -C './client/repo' remote prune server
git -C './client/repo' branch --list --all --verbose --verbose
git -C './client/repo' tag --list
What did you expect to happen? (Expected behavior)
https://git-scm.com/docs/git-remote says:
`git remote prune <remote>…` is equivalent to `git fetch --prune
<remote>`, except that no new references will be fetched.
so:
`git remote prune <remote>…` should prune tags when `fetch.pruneTags` is `true`.
(`git remote prune <remote>…` should prune tags when
`remote.server.fetch` has `+refs/tags/*:refs/tags/*`.)
`git fetch --dry-run` should print same tag once.
What happened instead? (Actual behavior)
Setting `fetch.pruneTags` to `true` does not make `git remote prune
<remote>…` prune tags.
(`git remote prune <remote>…` prunes tags when `remote.server.fetch`
has `+refs/tags/*:refs/tags/*`.)
`git fetch --dry-run` prints same tag twice.
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
reply other threads:[~2024-09-04 0:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANrWfmR1nTDF-ts3n2PpH2C+uvBzDm7ZEXh0StuwPZRmm80T1A@mail.gmail.com \
--to=jhcarl0814@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).