Re: finding earliest tags descended from a given commit

From: Shawn O. Pearce <spearce@spearce.org>
Date: Jan 27, 2007, 04:55 UTC
Message-ID: <20070127045552.GB9966@spearce.org>
In-Reply-To: <20070127044246.GC14205@fieldses.org>

"J. Bruce Fields" <bfields@fieldses.org> wrote:

Show 7 quoted lines

> That's interesting, I hadn't noticed name-rev before you and Shawn
> mentioned it.
> 
> It only finds one name, though. When I tried it just now on my
> repository what it found was a tag I'd created for an experimental
> version, which probably wouldn't be what I wanted.  (Though it might be,
> in some situations.)

Yea. Hmm. Maybe name-rev needs to learn a few more tricks, like favoring annotated tags over non-annotated ones/heads, and being able to print the top n nearest matches (e.g. 10), by displaying only one line of output per tag (or ref).

Right now I'm trying to educate describe some more. Although similar, describe has a much easier job as its very easy for it to say "that's the best name we have for the input". Part of that is because it is favoring annotated tags all of the time, and part of that is because it does this distance computation thing now and always favors the tag with the shortest distance between the tag and the input.

In the case of name-rev I'm thinking maybe its actually the longest distance annotated tag that makes sense. That is, prefer to name the input using the annotated tag which has the shortest distance between the tag and the input, but where the tag is the farthest back in history you can go when compared to any other possible tag, and yet stills contains the input in its ancestry.

-- 
Shawn.