Git development
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Martin Langhoff <martin.langhoff@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git describe oddity: ignoring recent tags...
Date: Mon, 23 Nov 2009 13:39:39 +0100	[thread overview]
Message-ID: <200911231339.41290.trast@student.ethz.ch> (raw)
In-Reply-To: <20091123123048.GA10172@atjola.homenet>

Björn Steinbrink wrote:
> On 2009.11.23 13:01:51 +0100, Martin Langhoff wrote:
> > git describe origin/master will respond olpc-update-2.16-20-g2d4e4b8
> > when it is fairly clear to me that it should be
> > olpc-update-2.19-1g<hash>.
[...]
> They are lightweight:
> $ git cat-file -t olpc-update-2.19
> commit
> 
> And using --tags "helps" here:
> $ git describe 
> olpc-update-2.16-20-g2d4e4b8
> 
> $ git describe --tags
> olpc-update-2.19-3-g2d4e4b8

Note that Gits that do not have 7e425c4 (describe: Make --tags and
--all match lightweight tags more often, 2008-10-13; first released in
1.6.1) will prefer the annotated tag over the unannotated ones even
with --tags, which explains your observation

> > For some reason, recent tags are being ignored -- and cgit even
> > displays them differently in
> > http://dev.laptop.org/git/projects/olpc-update/log/ though it is
> > unclear to me why.

at least with the first Git version mentioned:

> > Tested with 1.6.0.6 (Fedora 9 rpm) and 1.6.3.1.26.gf5b223 (on Karmic).

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

      parent reply	other threads:[~2009-11-23 12:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23 12:01 git describe oddity: ignoring recent tags Martin Langhoff
2009-11-23 12:30 ` Björn Steinbrink
2009-11-23 12:38   ` Martin Langhoff
2009-11-23 12:39   ` Thomas Rast [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=200911231339.41290.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=B.Steinbrink@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@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