From: Shawn O. Pearce <spearce@spearce.org>
Date: Sun, 11 Apr 2010 00:28:25 GMT
Subject: Re: git describe bug?
Message-ID: <20100411002825.GA23075@spearce.org>
In-Reply-To: <4BBB0377.8080007@op5.se>

Andreas Ericsson <ae@op5.se> wrote:
> Right now the behaviour is inconsistent.
...
> So as you can see, something else is going on. Both tags here are
> stashed as loose objects and both refs are unpacked.

Its the order the names were iterated out of the directory by
readdir().  Or the order they were sorted by lexographical ordering
during for_each_ref().  I can't remember if for_each_ref() sorts
the items before processing.

But either describe uses the first item it found for a given commit
if they have the same priority.  There's no notion of date being
factored into the decision of which tag to keep.

I'll work up a patch right now.

-- 
Shawn.