On Tue, May 04, 2010 at 11:26:23AM -0700, Jacob Helwig wrote: > 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? > [...] > 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.
All of the above is correct. >From the perspective of language implementations (that are under development and want to be able to access revisions of Parrot between releases), the SHA1 history/commit sequence of Parrot's master repository -- wherever it happens to be -- would likely be sufficient. At any rate, Rakudo would be able to find a way to work around the loss of svn revision numbers, and presumably other languages could follow suit. Much of this topic has already been discussed as objections #6 and #7 in http://trac.parrot.org/parrot/wiki/GitObjections . Pm _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
