diff --git a/docs/bugs.html b/docs/bugs.html index 9c9ab517d..6a2516ff3 100644 --- a/docs/bugs.html +++ b/docs/bugs.html @@ -285,7 +285,7 @@

If you aren't satisfied with just filing a bug report, you can try to find the cause of the problem and provide a fix yourself. - The best way to do that is by working with the latest code from CVS. + The best way to do that is by working with the latest code from Subversion. Alternatively, you can work with the source code available from the source distributions. If you @@ -305,12 +305,12 @@ to your message subject. Please include any relevant bug numbers. Patch files should be created with the -u option of the - diff or cvs diff command. For + diff or svn diff command. For example:

diff -u Javac.java.orig Javac.java > javac.diffs

- or, if you have source from SVN:

+ or, if you have source from Subversion:

svn diff Javac.java > javac.diffs

diff --git a/xdocs/bugs.xml b/xdocs/bugs.xml index b018fe1d8..f3ef6de3f 100644 --- a/xdocs/bugs.xml +++ b/xdocs/bugs.xml @@ -126,7 +126,7 @@

If you aren't satisfied with just filing a bug report, you can try to find the cause of the problem and provide a fix yourself. - The best way to do that is by working with the latest code from CVS. + The best way to do that is by working with the latest code from Subversion. Alternatively, you can work with the source code available from the source distributions. If you @@ -146,12 +146,12 @@ to your message subject. Please include any relevant bug numbers. Patch files should be created with the -u option of the - diff or cvs diff command. For + diff or svn diff command. For example:



diff -u Javac.java.orig Javac.java > javac.diffs



- or, if you have source from SVN:



+ or, if you have source from Subversion:



svn diff Javac.java > javac.diffs