Hello Johannes,

Johannes Schindelin wrote:
quoted text
> > But if I'd really prefer to know the "oldest" tag that includes the
> > given rev, I don't want that weighting.  I will try to come up with a
> > patch that introduces a flag.
> 
> The problem is: what is oldest?  We cannot rely on the timestamps.  And 
> doing the naive thing -- counting edges in the commit graph (in effect 
> using a weighting of 1) -- ends up in ugly names such as
> 
> 	tags/v2.6.22-rc1~1^2^2^2~11^2~13^2~8^2~1^3~5
That's what I meant.  I only want to make a statement like:

	If you want feature xy, you need to update to at least
	v2.6.22-rc1.
	
So the exact revision is not interesting to me.
 
quoted text
> Besides, you successfully hid from yours truly what your hypothetic flag 
> should accomplish.
I didn't think deeply about it, but there was a similar discussion for
git describe which implied counting refs on all paths leading to a given
tag.  It might be different here, as we look in the other direction.

Best regards
Uwe

-- 
Uwe Kleine-K