From: "André Kießling" <akiessling@carneios.de>
To: git@vger.kernel.org
Subject: Bug!?: Refspec '+' should be same as '--force' but is not
Date: Tue, 15 Sep 2026 17:06:38 +0200 [thread overview]
Message-ID: <1bcb043e-e744-4e01-8569-4da5669d25fc@carneios.de> (raw)
Hi there, think I found a bug...
In https://git-scm.com/docs/git-push I find:
> The + is optional and does the same thing as --force.
The fetch documentation refers to push for the details of <refspec> so I
assume, the statement also holds for fetch refspecs.
However, this is not true:
When I run `git fetch origin --tags --force` it will force update tags
that changed on remote (as expected) but will NOT delete local tags.
When I run `git fetch origin` with config set to `remote.origin.fetch =
+refs/tags/*:refs/tags/*` it will delete my local tags as if prune was set.
I'm using Git 2.54.0.windows.1
Carneios GmbH
Am Borsigturm 64
13507 Berlin
Tel. +49 30 2332035-0
Fax +49 30 2332035-99
https://www.carneios.de
info@carneios.de
Geschäftsführer: Michael Giersch
Handelsregister: Charlottenburg HRB 138285
USt.-ID: DE 280 745 293
next reply other threads:[~2026-09-15 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 15:06 André Kießling [this message]
2026-09-15 16:41 ` Bug!?: Refspec '+' should be same as '--force' but is not Ben Knoble
2026-09-15 19:34 ` Junio C Hamano
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=1bcb043e-e744-4e01-8569-4da5669d25fc@carneios.de \
--to=akiessling@carneios.de \
--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