Piotr Roszatycki wrote:
> On Friday 07 of October 2005 16:23, Wez Furlong wrote:
> 
>>I honestly don't see how it will be any better than CVS, if the data
>>comes from CVS in the first place.
>>
>>Since we've generally got our plates full, we don't have the resources
>>to support third parties maintaining their own forks.  We'd much
>>rather have those third parties working directly with us so that forks
>>are not necessary.
> 
> 
> I should redirect you to SVK website (http://svk.elixus.org/) and especially 
> to http://svk.elixus.org/?SingleUserSVK 
> http://svk.elixus.org/?SyncReposBetweenServers and 
> http://svk.elixus.org/?SVKAsAProxyForCVSMirror
> This is the better tool and designer to make the life much simpler, not more 
> complicated.
> 
> I.e. with CVS you can't get the diff of one commit for more that one file, 
> because the revisions are per file, not per repository. You can't find which 
> files was modified i.e. with "Fixed bug #34358" message without cvs2cl tool. 
> You have to dig the CVS repository and carefully read the log messages. It is 
> just one operation with Subversion.
> 
> Why don't you just provide the CVS tarball like for Sourceforge's projects? 
> Theirs tarballs are available as 
> http://cvs.sourceforge.net/cvstarballs/PROJECTNAME-cvsroot.tar.bz2

Just use cvsup: http://www.php.net/cvsup.php

-Rasmus

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to