[PATCH v5 6/9] push doc: move mention of "tag <tag>" later in the prose
- From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
- Date
- Aug 31, 2018, 20:10 UTC
- Message-ID
- <20180831201004.12087-7-avarab@gmail.com>
- In-Reply-To
- <20180830201244.25759-1-avarab@gmail.com>
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> --- Documentation/git-push.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 83e499ee97..71c78ac1a4 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -80,8 +80,6 @@ a tag (annotated or lightweight), and then only if it can fast-forward the <dst> ref even if it is not allowed by default (e.g., it is not a fast-forward.). + -`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`. -+ Pushing an empty <src> allows you to delete the <dst> ref from the remote repository. + @@ -89,6 +87,8 @@ The special refspec `:` (or `+:` to allow non-fast-forward updates) directs Git to push "matching" branches: for every branch that exists on the local side, the remote side is updated if a branch of the same name already exists on the remote side. ++ +`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`. --all:: Push all branches (i.e. refs under `refs/heads/`); cannot be
-- 2.19.0.rc1.350.ge57e33dbd1