git/list[1] front-page[2] threads[3] people[4] search[5] about
 

name-rev does not show the shortest path

From
Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
Date
Aug 23, 2007, 10:38 UTC
Message-ID
<20070823103817.GF6573@informatik.uni-freiburg.de>
Hello,

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.
BTW: gitk does the right thing, it says:
	Follows: v2.6.21-rc7
	Precedes: v2.6.22-rc1
(called with 
	zeisberg@cassiopeia:~/gsrc/linux-2.6$ gitk 0567a0c022d5b343370a343121f38fd89925de55^..0567a0c022d5b343370a343121f38fd89925de55
)
I didn't check how it does that though.

Best regards Uwe

-- 
Uwe Kleine-König

exit vi, lesson I:
: q ! <CR>
Next: Julian Phillips
Message 1 of 13 in “name-rev does not show the shortest path”
  1. Uwe Kleine-KönigAug 23, 2007
  2. Julian PhillipsAug 24, 2007
  3. Uwe Kleine-KönigAug 24, 2007
  4. Julian PhillipsAug 24, 2007
  5. Junio C HamanoAug 24, 2007
  6. Johannes SchindelinAug 25, 2007
  7. Jeff KingAug 26, 2007
  8. Johannes SchindelinAug 26, 2007
  9. Jeff KingAug 27, 2007
  10. Johannes SchindelinAug 27, 2007
  11. Johannes SchindelinAug 27, 2007
  12. name-rev: Fix non-shortest descriptionJohannes Schindelin, Aug 27, 2007
  13. Uwe Kleine-KönigAug 27, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.