[PATCH] Remarks that tags need to be pushed explicitly
- From
- Steffen Daode Nurpmeso <sdaoden@googlemail.com>
- Date
- Jun 7, 2011, 15:33 UTC
- Message-ID
- <20110607153323.GA71116@sherwood.local>
- In-Reply-To
- <7vk4cx7mst.fsf@alter.siamese.dyndns.org>
@ Junio C Hamano <gitster@pobox.com> wrote (2011-06-07 16:12+0200):
> > diff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt > This feels way out of place in the context of the story the tutorial is > telling.
No door gap at all for this in *tut* and user-manual!
> How about adding an example in git-push section instead?
I'll pack this in verbatim. :). You'll notice that the patch also adds the word "Utilize" in front of `tag <tag>` in the OPTIONS section. I did not even now that the term "tag" can be used, but i'm afraid that i thought of that as a spelling error - on my terminal all these `terms` are not highlighted in any special way. 'Would thus be good? __ Ciao, Steffen sdaoden(*)(gmail.com) () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
Signed-off-by: Steffen Daode Nurpmeso <sdaoden@gmail.com> --- Documentation/git-push.txt | 7 ++++++- Documentation/git-tag.txt | 3 ++- 2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 88acfcd..898348a 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -55,7 +55,7 @@ you can tell git to update the <dst> ref even when the update is not a fast-forward. This does *not* attempt to merge <src> into <dst>. See EXAMPLES below for details. + -`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`. +Utilize `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. @@ -371,6 +371,11 @@ git push origin HEAD:master:: `origin` repository. This form is convenient to push the current branch without thinking about its local name. +git push origin tag v1.5:: + Push the `v1.5` tag to the `origin` repository. A newly created + tag needs to be published explicitly like this, just like a newly + created branch does not get published automatically. + git push origin master:refs/heads/experimental:: Create the branch `experimental` in the `origin` repository by copying the current `master` branch. This form is only diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt index d82f621..242837f 100644 --- a/Documentation/git-tag.txt +++ b/Documentation/git-tag.txt @@ -27,7 +27,8 @@ Unless `-f` is given, the tag to be created must not yet exist in the If one of `-a`, `-s`, or `-u <key-id>` is passed, the command creates a 'tag' object, and requires a tag message. Unless `-m <msg>` or `-F <file>` is given, an editor is started for the user to type -in the tag message. +in the tag message. Tag objects can be pushed upstream with +linkgit:git-push[1]. If `-m <msg>` or `-F <file>` is given and `-a`, `-s`, and `-u <key-id>` are absent, `-a` is implied.
-- 1.7.6.rc0