Make the description of pushing tags easier to read, but move the shorthand notation towards the end of the description. This gives a better flow. Signed-off-by: Anders Melchiorsen <mail@xxxxxxxxxxxxxxxx> --- Documentation/git-push.txt | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-) diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 9788d49..52035db 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -38,7 +38,7 @@ OPTIONS by the source ref, followed by a colon `:`, followed by the destination ref. + -The <src> side represents the source branch that you +The <src> side represents the source branch or tag that you want to push. The <dst> side represents the destination location. + The local ref that matches <src> is used @@ -46,8 +46,6 @@ to fast forward the remote ref that matches <dst>. If the optional leading plus `+` is used, the remote ref is updated even if it does not result in a fast forward update. + -`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`. -+ A parameter <ref> without a colon pushes the <ref> from the source repository to the destination repository under the same name. + @@ -64,6 +62,10 @@ nor in any Push line of the corresponding remotes file---see below). The <src> can be an arbitrary "SHA1 expression", such as `HEAD` or `master~4` (see linkgit:git-rev-parse[1]). In this case, a <dst> location has to be named. ++ +When pushing tags, `tag <tag>` can be used as a shorthand for +`refs/tags/<tag>:refs/tags/<tag>`. This should be specified as +two arguments (that is, without quotes in the shell). --all:: Instead of naming each ref to push, specifies that all -- 1.6.0.2.514.g23abd3 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
