From: Marc Branchaud <marcnarc@xiplink.com>
To: Daniele Segato <daniele.segato@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] git-tag man: when to use lightweight or annotated tags
Date: Thu, 25 Jul 2013 10:47:43 -0400 [thread overview]
Message-ID: <51F13A8F.9040400@xiplink.com> (raw)
In-Reply-To: <51F12BE6.80606@gmail.com>
On 13-07-25 09:45 AM, Daniele Segato wrote:
> 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.
Unfortunately the word "annotated" hasn't yet been introduced at this point,
so the overall effect is even more confusing. Also, I find the "release" vs.
"random" distinction a bit misleading since both types of tag can refer to
any object. I also liked the direction of your earlier "command only
consider annotated tags by default" phrasing.
After reading the Tagging section of the Git Book[1] I came up with the
following. Feel free to modify it as you like, or ignore it completely:
Tag objects (created with -a) are called annotated tags. While a lightweight
tag is simply a name for an object (usually a commit object), an annotated
tag contains the creation date, the tagger's name and e-mail, a tagging
message, and can be signed and verified with GNU Privacy Guard (GnuPG). Most
git commands only consider annotated tags by default. In general lightweight
tags are for private or temporary object labels, while annotated tags are
meant to be permanent and/or published. For example, an annotated tag is
normally used to identify a release point.
M.
[1] http://git-scm.com/book/en/Git-Basics-Tagging
next prev parent reply other threads:[~2013-07-25 14:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 10:17 git tag usability issue: Lightweight vs Annotated confusion for the end user (ex. git describe default) Daniele Segato
2013-07-24 20:34 ` Junio C Hamano
2013-07-25 13:45 ` [PATCH] git-tag man: when to use lightweight or annotated tags Daniele Segato
2013-07-25 14:47 ` Marc Branchaud [this message]
2013-07-26 8:44 ` Daniele Segato
2013-07-26 8:46 ` Daniele Segato
2013-07-26 14:51 ` Marc Branchaud
2013-07-26 17:19 ` Daniele Segato
2013-07-26 17:33 ` [PATCHv3] " Daniele Segato
2013-07-26 19:06 ` Jeff King
2013-07-26 19:36 ` Jonathan Nieder
2013-07-29 18:02 ` Daniele Segato
2013-08-07 12:32 ` Daniele Segato
2013-07-26 21:13 ` Marc Branchaud
2013-07-29 15:04 ` Junio C Hamano
2013-07-29 18:20 ` Daniele Segato
2013-07-27 10:39 ` Daniele Segato
2013-07-27 11:26 ` Philip Oakley
2013-07-27 11:45 ` Stefan Beller
2013-07-29 18:16 ` Daniele Segato
2013-07-26 21:13 ` [PATCH] " Marc Branchaud
2013-07-29 18:21 ` Daniele Segato
2013-07-25 13:48 ` git tag usability issue: Lightweight vs Annotated confusion for the end user (ex. git describe default) Daniele Segato
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=51F13A8F.9040400@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=daniele.segato@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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).