push doc: remove confusing mention of remote merger
Saying that "git push <remote> <src>:<dst>" won't push a merger of <src> and <dst> to <dst> is clear from the rest of the context here, so mentioning it is redundant, furthermore the mention of "EXAMPLES below" isn't specific or useful. This phrase was originally added in 149f6ddfb3 ("Docs: Expand explanation of the use of + in git push refspecs.", 2009-02-19), as can be seen in that change the point of the example being cited was to show that force pushing can leave unreferenced commits on the remote. It's enough that we explain that in its own section, it doesn't need to be mentioned here. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Ævar Arnfjörð Bjarmason committed
Aug 31, 2018 at 20:10 UTC
d931455acf1cf1a21a4f10fd99fc2bd9bbefa7a9
1 file changed
+1
-2
Documentation/git-push.txt
+1
-2
@@ -78,8 +78,7 @@ on the remote side. By default this is only allowed if <dst> is not
78
a tag (annotated or lightweight), and then only if it can fast-forward
79
<dst>. By having the optional leading `+`, you can tell Git to update
80
the <dst> ref even if it is not allowed by default (e.g., it is not a
81
-fast-forward.) This does *not* attempt to merge <src> into <dst>. See
82
-EXAMPLES below for details.
81
+fast-forward.).
82
+
83
`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
84
+