Re: name-rev does not show the shortest path
- From
Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
- Date
- Aug 24, 2007, 12:52 UTC
- Message-ID
- <20070824125230.GA12030@informatik.uni-freiburg.de>
- In-Reply-To
- <Pine.LNX.4.64.0708241253050.8987@reaper.quantumfyre.co.uk>
Hello Julian,
Julian Phillips wrote:
Show 24 quoted lines
> On Thu, 23 Aug 2007, Uwe Kleine-König wrote: > >I want to check to which kernel version I need to upgrade to get a > >certain feature. For my case it was introduced in 0567a0c022d5b. > > > > zeisberg@cassiopeia:~/gsrc/linux-2.6$ > > rev=0567a0c022d5b343370a343121f38fd89925de55 > > > > zeisberg@cassiopeia:~/gsrc/linux-2.6$ git name-rev --tags $rev > > 0567a0c022d5b343370a343121f38fd89925de55 tags/v2.6.22~1686^2~1^3~5 > > > > zeisberg@cassiopeia:~/gsrc/linux-2.6$ git name-rev --refs=*-rc1 $rev > > 0567a0c022d5b343370a343121f38fd89925de55 > > tags/v2.6.22-rc1~1009^2~1^3~5 > > > >I don't now the underlaying algorithm, maybe it's to get a short string? > > > >Anyhow I want to know the earliest tag that includes this patch? Is > >there something I missed? > > > >I remember there was a similar discussion regarding describe. > > git describe --contains 0567a0c022d5b > > probably a 1.5.3 feature? (certainly doesn't exist in 1.5.2.2)
That command says v2.6.22~1686^2~1^3~5, too. That is, it doesn't use the "older" v2.6.22-rc1 tag as a basis.
Best regards Uwe
-- Uwe Kleine-König http://www.google.com/search?q=1+degree+celsius+in+kelvin