# SVN Conversion Complete

- Thread: https://externals.io/message/44933
- Original archive: https://news-web.php.net/php.internals/44933
- Started by Gwynne Raskind on 2009-07-11T01:29:50+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #44933 — Gwynne Raskind — 2009-07-11T01:29:50+00:00

URL: https://externals.io/message/44933#44933

The conversion from CVS to SVN is complete. CVS read AND write access  
has been completely disabled. SVN is now up and running, however *we  
remain in commit freeze* until Monday. Commits to SVN in order to fix  
critical problems (such as all those scripts which should have been  
made ready a long time ago) are accepted.

All information on the subject is available at http://wiki.php.net/vcs/svnfaq 
.

The SVN repository URL is http://svn.php.net/repository.
The ViewVC (SVN) URL is http://svn.php.net.

Once again, ONLY commits that relate to fixing CVS->SVN migration  
issues are allowed. We remain in commit freeze.

Everyone who has issues, please put them on svn- 
migration@lists.php.net. I'll be around all weekend, and all of us  
will respond to issues as quickly as we can.

-- Gwynne

---

## #44934 — Jani Taskinen — 2009-07-11T10:09:26+00:00

URL: https://externals.io/message/44933#44934 · In reply to: #44933

Gwynne Raskind kirjoitti:
> The conversion from CVS to SVN is complete. CVS read AND write access 
> has been completely disabled. SVN is now up and running, however *we 

Why is CVS read access disabled? I had some patches brewing in my checkouts and 
getting them "out" now is kinda PITA.. Also checking that the conversion 
actually worked would be easier when one could compare the logs and such..

--Jani