On Wed, 2007-05-30 at 01:29 -0700, Rasmus Lerdorf wrote: > Well, the problem is that if the work involved to do this is in any way > CVS-specific, it will be throw-away work once we move away from CVS, > which is inevitable. What we don't know at this point is the lifespan > of CVS. I'm unmotivated to do anything with SVN with the major 1.5
You keep repeating "inevitable", but exactly what is the "inevitable" here? AFAIK, CVS works fine: don't fix if it isn't broken! I'd like to here the (real) reasons why the switch would be beneficial for project like PHP. I'm using both CVS and SVN daily, but I still prefer CVS..perhaps I'm just old-fashioned..:) --Jani -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
