[PATCH] git-tag man: when to use lightweight or annotated tags

From: Daniele Segato <daniele.segato@gmail.com>
Date: Jul 25, 2013, 13:45 UTC
Message-ID: <51F12BE6.80606@gmail.com>
In-Reply-To: <7vtxjj66kn.fsf@alter.siamese.dyndns.org>

 From d0f4eca712e7cf74286bfab306763a8a571b6c95 Mon Sep 17 00:00:00 2001
From: Daniele Segato <daniele.segato@gmail.com>
Date: Thu, 25 Jul 2013 15:33:18 +0200
Subject: [PATCH] git-tag man: when to use lightweight or annotated tags

stress the difference between the two with suggestion on when the user should use one in place of the other.

Signed-off-by: Daniele Segato <daniele.segato@gmail.com>
---
  Documentation/git-tag.txt |    4 ++++
  1 file changed, 4 insertions(+)

diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt
index 22894cb..48f5504 100644
--- a/Documentation/git-tag.txt
+++ b/Documentation/git-tag.txt
@@ -36,6 +36,10 @@ are absent, `-a` is implied.
  Otherwise just a tag reference for the SHA-1 object name of the commit 
object is
  created (i.e. a lightweight tag).

+Annotated and Lightweight tags are not the same thing for git and you 
shouldn't
+mix them up. Annotated tags are meant for release while lightweight 
tags are
+meant to tag random commits.
+
  A GnuPG signed tag object will be created when `-s` or `-u
  <key-id>` is used.  When `-u <key-id>` is not used, the
  committer identity for the current user is used to find the

-- 
1.7.10.4