On 5/30/07, Steph Fox <[EMAIL PROTECTED]> wrote:
Given that this entire thread came about because at least two of the core team don't have time to deal with merging to HEAD, that doesn't seem very likely. But you're right to put an end to quick-fix and possibly cvs-specific solutions. Does svn even support validation scripting? Does anyone even know without checking?
The code to do the first part of what I described is just a bit perl, or can be easily tweaked to perl, and run in our environment without too much hassle. It will be marginally cvs dependent, but less work that making it work for svn; I think its totally worth it. SVN does indeed support validation... how else do you think we implement the checks I described earlier in the thread? :-)
Lukas was onto a good thing with his idea of moving less challenging areas of the CVS repository to SVN first IMHO. It'll make the task of moving the difficult ones less horrendous, and it'll give some idea of the problems likely to be encountered in adoption (if any).
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 :) --Wez. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
