git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Daode Nurpmeso <sdaoden@googlemail.com>
To: git@vger.kernel.org
Cc: Steffen Daode Nurpmeso <sdaoden@gmail.com>
Subject: [PATCH] Notes that tags need to pushed explicitely
Date: Tue,  7 Jun 2011 12:48:33 +0200	[thread overview]
Message-ID: <1307443713-14534-1-git-send-email-sdaoden@gmail.com> (raw)
In-Reply-To: <20110606130205.GA41674@sherwood.local>

---
 Documentation/git-tag.txt     |    3 ++-
 Documentation/gittutorial.txt |    1 +
 2 files changed, 3 insertions(+), 1 deletions(-)

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.
diff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt
index 0982f74..08c0c3a 100644
--- a/Documentation/gittutorial.txt
+++ b/Documentation/gittutorial.txt
@@ -520,6 +520,7 @@ names.  For example:
 
 -------------------------------------
 $ git diff v2.5 HEAD	 # compare the current HEAD to v2.5
+$ git push v2.5		 # push the tag upstream
 $ git branch stable v2.5 # start a new branch named "stable" based
 			 # at v2.5
 $ git reset --hard HEAD^ # reset your current branch and working
-- 
1.7.6.rc0

  parent reply	other threads:[~2011-06-07 10:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 13:02 Jabber, question on push,pull and --tags, and no help but jabber Steffen Daode Nurpmeso
2011-06-06 14:31 ` Michael J Gruber
2011-06-06 15:21   ` Felipe Contreras
2011-06-06 21:46   ` Steffen Daode Nurpmeso
2011-06-07  5:47     ` Michael J Gruber
2011-06-07 10:24       ` Steffen Daode Nurpmeso
     [not found] ` <9215090.63086.1307370716794.JavaMail.trustmail@mail1.terreactive.ch>
2011-06-06 15:34   ` Victor Engmark
2011-06-06 17:58     ` Junio C Hamano
2011-06-07 10:48 ` Steffen Daode Nurpmeso [this message]
2011-06-07 14:12   ` [PATCH] Notes that tags need to pushed explicitely Junio C Hamano
2011-06-07 15:33     ` [PATCH] Remarks that tags need to be pushed explicitly Steffen Daode Nurpmeso
2011-06-10 20:39     ` [PATCH v2] " Steffen Daode Nurpmeso
2011-06-10 21:24       ` Junio C Hamano
2011-06-11 17:20         ` Steffen Daode Nurpmeso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1307443713-14534-1-git-send-email-sdaoden@gmail.com \
    --to=sdaoden@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=sdaoden@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).