git describe oddity: ignoring recent tags...

Clone this repo: git://dev.laptop.org/projects/olpc-update -- or just
check visually the recent history here
http://dev.laptop.org/git/projects/olpc-update/log/

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>.

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.

These tags are not 'lightweight', and no tags are signed either.
Passing --tags and --debug has not helped much.

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



m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

On 2009.11.23 13:01:51 +0100, Martin Langhoff wrote:

Clone this repo: git://dev.laptop.org/projects/olpc-update -- or just
check visually the recent history here
http://dev.laptop.org/git/projects/olpc-update/log/

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>.

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.

These tags are not 'lightweight', and no tags are signed either.
Passing --tags and --debug has not helped much.

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

Bjoern

2009/11/23 Björn Steinbrink [off-list ref]:

They are lightweight:
$ git cat-file -t olpc-update-2.19
commit

Hmmm. I thought a tag with a _message_ was not lightweight.

$ git tag -ln
...
olpc-update-2.16 Release 2.16
olpc-update-2.17 Release 2.17.
olpc-update-2.18 Rlease 2.18.
olpc-update-2.19 Release 2.19.

Argh... I see now - git tag is being helpful and showing the first
line of the commit msg instead of the tag msg, so I thought they were
full tags.

DWIM bites again! ;-(

And using --tags "helps" here:
$ git describe
olpc-update-2.16-20-g2d4e4b8

$ git describe --tags
olpc-update-2.19-3-g2d4e4b8

Right. Doesn't make a difference with 1.6.0.6 but it does with
1.6.3.1.26.gf5b223



m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

Björn Steinbrink wrote:

On 2009.11.23 13:01:51 +0100, Martin Langhoff wrote:

quoted

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

quoted

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:

quoted

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