On Tue, May 4, 2010 at 10:02, Gerd Pokorra <[email protected]> wrote: > I like the git commands. I think they are alike the svn commands. > But by git I am missing the revision number. I like the increasing > revision number by svn and the possibility to specify it as option (svn > -r <revision>). It is very helpful or the basic of languages that use > Parrot. Is there something similar in git? > > Gerd >
That really depends on what you're trying to do with the revision number. "svn -r <revision>" isn't actually a valid command in SVN as far as I know. If you're asking how to use the SHA1s in git commands, then we'd need to know what you were trying to actually do, or find out before giving an example. The commit SHA1s can still be used for checking out code, doing logs/cherry-picks/merges/etc. They aren't as obvious at a glance which one is "newer", but that's partially because Git is a distributed system, and "newer" takes on a more nuanced meaning. If you're asking "Can git have increasing (global) revision numbers like SVN for the commits?", then the answer is "No, nor can any truly distributed revision control system." You can have locally increasing revision numbers (IIRC, Hg does this), but they will not be guaranteed to be the same across different copies of the repository. _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
