Re: git describe bug?

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Shawn O. Pearce
Date: Saturday, April 10, 2010 - 5:28 pm

Andreas Ericsson <ae@op5.se> wrote:
...

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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
git describe bug?, Dustin Sallings, (Fri Apr 2, 10:20 am)
Re: git describe bug?, Shawn O. Pearce, (Fri Apr 2, 11:31 am)
Re: git describe bug?, Andreas Ericsson, (Tue Apr 6, 2:48 am)
Re: git describe bug?, Shawn O. Pearce, (Sat Apr 10, 5:28 pm)
[PATCH] describe: Break annotated tag ties by tagger date, Shawn O. Pearce, (Sat Apr 10, 6:54 pm)
[PATCH v2 1/5] tag.c: Correct indentation, Shawn O. Pearce, (Mon Apr 12, 4:25 pm)
[PATCH v2 2/5] tag.h: Remove unused signature field, Shawn O. Pearce, (Mon Apr 12, 4:25 pm)
[PATCH v2 4/5] tag.c: Parse tagger date (if present), Shawn O. Pearce, (Mon Apr 12, 4:25 pm)