On Tue, Aug 28, 2007 at 10:54:43AM +0200, Uwe Kleine-König wrote: > > 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. Isn't that what name-rev already does? As long as your tags are linear (that is, v2.6.22-rc2 contains all of v2.6.22-rc1, which contains all of v2.6.21, etc), then it should give you the "closest" tag that contains the commit you specified. If there is another tag which also contains the revision but is "less close" than the one reported, then it's not going to be the oldest. If your tags represent different branches, I suspect you can come up with some corner cases that won't obey this property. -Peff - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
