Hello Jeff, Jeff King wrote: > 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? This is what this thread is all about, isn't it? If I believed it, I would have said: to have the feature that was introduced in 0567a0c022, you need at least v2.6.22: zeisberg@cassiopeia:~/gsrc/linux-2.6$ git name-rev --tags $rev 0567a0c022d5b343370a343121f38fd89925de55 tags/v2.6.22~1686^2~1^3~5 But actually v2.6.22-rc1 is enough ... > 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. ... even though: zeisberg@cassiopeia:~/gsrc/linux-2.6$ git rev-list v2.6.22..v2.6.22-rc1 | wc -l 0 or did I get something wrong? Best regards Uwe -- Uwe Kleine-König exit vi, lesson V: o : q ! CTRL-V <CR> <Esc> " d d d @ d - 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
