push doc: move mention of "tag <tag>" later in the prose
This change will be followed-up with a subsequent change where I'll change both sides of this mention of "tag <tag>" to be something that's best read without interruption. To make that change smaller, let's move this mention of "tag <tag>" to the end of the "<refspec>..." section, it's now somewhere in the middle. 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
8da6128c264c7896c011b5e3e0eace57eb073f63
1 file changed
+2
-2
Documentation/git-push.txt
+2
-2
@@ -80,8 +80,6 @@ a tag (annotated or lightweight), and then only if it can fast-forward
80
the <dst> ref even if it is not allowed by default (e.g., it is not a
81
fast-forward.).
82
+
83
-`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
84
-+
83
Pushing an empty <src> allows you to delete the <dst> ref from
84
the remote repository.
85
+
@@ -89,6 +87,8 @@ The special refspec `:` (or `+:` to allow non-fast-forward updates)
87
directs Git to push "matching" branches: for every branch that exists on
88
the local side, the remote side is updated if a branch of the same name
89
already exists on the remote side.
90
++
91
+`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
92
93
--all::
94
Push all branches (i.e. refs under `refs/heads/`); cannot be