Wez Furlong wrote: > As Rasmus said, it's a job for someone to sit down with a copy of the > repository, cvs2svn, a lot of time, and a lot of patience, to make the > migration work... but we're not stopping anyone from volunteering :)
I converted our company's CVS to SVN a while ago and might be willing to give it a try as I'm familiar with basic SVN setup, commit hooks and cvs2svn. I didn't follow this thread really so I'm not up-to-date with the requirements of the version control setup, i.e. what CVS features / view (web, anon and authenticated access) you currently use. Is there a summary of the requirements somewhere? Who's in charge of the CVS setup right now? - Chris -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
