summaryrefslogtreecommitdiffstats
path: root/pull-fetch-param.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2018-09-20 14:53:41 -0700
committerJunio C Hamano <gitster@pobox.com>2018-09-20 14:53:41 -0700
commitca9da32e093dafdac15a5b5bdd306d6435a524be (patch)
treeab198d718f0c4c74a85a1cec3b7dacabf07a8374 /pull-fetch-param.txt
parent980e61ec567f55c9247391052477e61a32d24548 (diff)
downloadgit-htmldocs-ca9da32e093dafdac15a5b5bdd306d6435a524be.tar.gz
Autogenerated HTML docs for v2.19.0-221-g150f3
Diffstat (limited to 'pull-fetch-param.txt')
-rw-r--r--pull-fetch-param.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/pull-fetch-param.txt b/pull-fetch-param.txt
index 293c6b967..7d3a60f5b 100644
--- a/pull-fetch-param.txt
+++ b/pull-fetch-param.txt
@@ -45,9 +45,9 @@ rules particular to 'git fetch' are noted below.
+
Until Git version 2.20, and unlike when pushing with
linkgit:git-push[1], any updates to `refs/tags/*` would be accepted
-without `+` in the refspec (or `--force`). The receiving promiscuously
+without `+` in the refspec (or `--force`). When fetching, we promiscuously
considered all tag updates from a remote to be forced fetches. Since
-Git version 2.20, fetching to update `refs/tags/*` work the same way
+Git version 2.20, fetching to update `refs/tags/*` works the same way
as when pushing. I.e. any updates will be rejected without `+` in the
refspec (or `--force`).
+