Re: git describe bug?

["Shawn O. Pearce" <spearce@spearce.org>]

Dustin Sallings <dustin@spy.net> wrote:
> 
> 	describe does not choose the most recent tag when multiple tags point to a single commit (for example, when an RC release becomes a proper release).
> 
> 	There's a bit of conflict in the documentation between the following:
> 
> 		``tags with newer dates will always be preferred over tags with older dates''
> 
> 	and the next sentence:
> 
> 		``If an exact match is found, its name will be output and searching will stop.''
> 
> 	The code does not allow for multiple exact matches, leading to what I would consider incorrect behavior as shown below:

Yes, I've seen this too.  IIRC we've actually discussed this in
the past.  I can't find the thread (my search skills are sub-par
despite who I work for...).  But the general idea if I remember
it right was we wanted to use the older tag, because that tag
came first.

So its probably more a documentation bug than a software bug.

-- 
Shawn.