Fix some more CVS references to SVN

git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@9615 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
Olly Betts 2006-12-14 02:38:11 +00:00
commit 55e97333c1
2 changed files with 4 additions and 4 deletions

View file

@ -3281,7 +3281,7 @@ If you wish for a new language module to be distributed with SWIG,
which we encourage for all popular languages, there are a few requirements.
While we appreciate that getting all aspects of a new language working
won't happen at the outset, there are a set of minimum requirements before
a module can be committed into the cvs repository for distribution with future
a module can be committed into the SVN repository for distribution with future
versions of SWIG. The following are really a summary of this whole section with
details being outlined earlier on.
</p>
@ -3323,7 +3323,7 @@ details being outlined earlier on.
</ol>
<p>
Once accepted into CVS, development efforts should concentrate on
Once accepted into SVN, development efforts should concentrate on
getting the entire test-suite to work with plenty of runtime tests.
Runtime tests should be for existing testcases and new test cases
should be added should there be an area not already covered by

View file

@ -215,8 +215,8 @@ The short abbreviated instructions follow...
</ul>
<p>
The step by step instructions to download and install MinGW and MSYS, then download and build the latest version of SWIG from cvs follow...
Note that the instructions for obtaining SWIG from CVS are also online at <a href="http://www.swig.org/cvs.html">SWIG CVS</a>.
The step by step instructions to download and install MinGW and MSYS, then download and build the latest version of SWIG from SVN follow...
Note that the instructions for obtaining SWIG from SVN are also online at <a href="http://www.swig.org/cvs.html">SWIG SVN</a>.
</p>
<p>