2008/7/25 Gwynne Raskind <[EMAIL PROTECTED]> > At this point it's clear that moving from CVS to SVN for PHP has become a > more or less official project. As such, there is a new mailing list < > [EMAIL PROTECTED]> for anyone who wants to help with the move. > If you're familiar with what I've already done so far (< > http://wiki.php.net/svnmigration>) and want to help, I beg you on my knees > to subscribe (send a mail to <[EMAIL PROTECTED]>) and > let us know what you want to do :). It's past time for PHP to make this step > a just a little bit further into the future and I hope we can work together > to make it happen. > > -- Gwynne, Daughter of the Code > "This whole world is an asylum for the incurable." > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > Hi.
I've been a client user of CVS (php) both SVN and git (strangely enough, for the same project - PrototypeJS). As a windows user my observations/opinions are ... 1 - CVS uses a version number for versions of a file and tags when branching is necessary. From what I can tell a group of change to many files are not grouped in any obvious way. TortoiseCVS integrates with the Windows Explorer environment. Command line tools are provided as TortoiseCVS uses them "behind the scenes". I've also got Cygwin's cvs. 2 - SVN uses a version number for versions of a file and uses directories when branching is necessary. Groups of changes are connected via a "changeset". TortoiseSVN integrates with the Windows Explorer environment in a similar method to that of TortoiseCVS. I've also got Cygwin's svn. 3 - GIT uses a SHA1 hash to group the changes. I find this next to useless to compare versions as there is no version number per se (at least not one I can see). I've only got git-gui for Windows. It works very differently to the Tortoise tools. Purely from my own experience and knowledge level, I like SVN. I like the idea of a group of changes being linked. I miss the version numbering (it may just be that Prototype don't need them ...). git feels very different to CSV and SVN. It may just be I need to change the way I see the information provided. If git can provide in-file version numbering (like CVS does), then that would feel more comfortable than the SHA1 hashes used. Richard. -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!"
