git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Erez Zilber <erezzi.list@gmail.com>
Cc: Pierre Habouzit <madcoder@debian.org>,
	"git@vger.kernel.org" <git@vger.kernel.org>,
	open-iscsi@googlegroups.com
Subject: Re: git-describe doesn't show the most recent tag
Date: Sun, 28 Sep 2008 16:51:31 +0200	[thread overview]
Message-ID: <48DF99F3.2070503@op5.se> (raw)
In-Reply-To: <ce513bcc0809280729p47cc3790nb77b3cae8b805221@mail.gmail.com>

Erez Zilber wrote:
> On Sun, Sep 28, 2008 at 4:55 PM, Pierre Habouzit <madcoder@debian.org> wrote:
>> On Sun, Sep 28, 2008 at 01:48:42PM +0000, Erez Zilber wrote:
>>> Why is this happening?
>>       --tags
>>           Instead of using only the annotated tags, use any tag found in
>>           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>           .git/refs/tags.
>>
> 
> I'm not sure that I understand the difference between tags and annotated tags.
> 

An annotated tag is one created with "git tag -a" or "git tag -s".
Other tags are considered "lightweight". They are supported for
creating immutable quick-and-dirty savepoints for private use,
while published tags are supposed to be annotated to give them
some extra weight.

You can use lightweight tags like normal tags (ie, and publish
them), but then some assumptions in git will not be correct and
you need to tell it so.

Btw, the default update hook prevents lightweight (unannotated)
tags from entering a repository you're pushing to, so this
assumption is not something that's unique to just "describe".

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

      parent reply	other threads:[~2008-09-28 14:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-28 13:48 git-describe doesn't show the most recent tag Erez Zilber
2008-09-28 13:55 ` Pierre Habouzit
2008-09-28 14:29   ` Erez Zilber
2008-09-28 14:39     ` Pierre Habouzit
2008-09-28 15:03       ` Pierre Habouzit
2008-09-28 15:12         ` [PATCH] doc: enhance git describe --tags help Pierre Habouzit
2008-09-29 15:01           ` Shawn O. Pearce
2008-09-30  8:39             ` Pierre Habouzit
2008-10-10 16:59               ` [RFC PATCH] describe: Make --tags and --all match lightweight tags more often Shawn O. Pearce
2008-10-10 17:12                 ` Pierre Habouzit
2008-10-10 18:18                   ` Junio C Hamano
2008-10-13 14:32                     ` Shawn O. Pearce
2008-10-13 14:39                   ` [PATCH v2] " Shawn O. Pearce
2008-10-15 12:54                     ` Santi Béjar
2008-10-11 22:47                 ` [RFC PATCH] " Andreas Ericsson
2008-10-12 18:00                   ` Shawn O. Pearce
2008-10-12 18:13                     ` Andreas Ericsson
2008-10-12 18:29                 ` Uwe Kleine-König
2008-09-30  9:56             ` [PATCH] doc: enhance git describe --tags help Uwe Kleine-König
2008-09-30 10:09               ` Andreas Ericsson
2008-09-30 19:04               ` Shawn O. Pearce
2008-09-30 22:14                 ` Uwe Kleine-König
2008-09-30 22:26                   ` Shawn O. Pearce
2008-10-15 20:05                     ` Uwe Kleine-König
2008-09-28 15:05       ` git-describe doesn't show the most recent tag Erez Zilber
2008-09-28 14:51     ` Andreas Ericsson [this message]

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=48DF99F3.2070503@op5.se \
    --to=ae@op5.se \
    --cc=erezzi.list@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=madcoder@debian.org \
    --cc=open-iscsi@googlegroups.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).