Junio C Hamano <gitster@xxxxxxxxx> writes: > Toralf Förster <toralf.foerster@xxxxxx> writes: > > > git-describe gives an informative string about the current status: > > tfoerste@n22 ~/devel/linux-2.6 $ git describe > > v2.6.26-rc9-56-g6329d30 > > > > I appended those strings to the names of my UML kernel executables. > > Unfortunately I didn't used the commit id and now I'm wondering whether git > > could accept v2.6.26-rc9-56 as well in future. > > It does take v2.6.26-rc9-56-g6329d30. > > It will never take v2.6.26-rc9-56. The world is not linear. Nevertheless it _could_ be unique. Besides, it would be nice to have some command (git-rev-parse perhaps?) which could take ambiguous commit-ish, and list all commit which matches it. -- Jakub Narebski Poland ShadeHawk on #git -- 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
