diff options
| -rw-r--r-- | doc/Netpbm.programming | 5 | ||||
| -rw-r--r-- | doc/USERDOC | 7 |
2 files changed, 3 insertions, 9 deletions
diff --git a/doc/Netpbm.programming b/doc/Netpbm.programming index bd1c3596..62e4c569 100644 --- a/doc/Netpbm.programming +++ b/doc/Netpbm.programming @@ -57,9 +57,8 @@ the conventional Unix means of communicating code changes. A Subversion You should update or create documentation too. But if you don't, the Netpbm maintainer will do the update before releasing your code. The source files for the documentation are the HTML files in the 'userguide' directory of the -Netpbm Subversion repository: -http://netpbm.svn.sourceforge.net/svnroot/netpbm/userguide . The identical -files are at http://netpbm.sourceforge.net/doc/ . +Netpbm Subversion repository: https://svn.code.sf.net/p/netpbm/code/userguide. +The identical files are at http://netpbm.sourceforge.net/doc/ . There are some automated tests in the package - shell scripts in files named such as "pbmtog3.test". You can use those to verify your diff --git a/doc/USERDOC b/doc/USERDOC index f067059a..9d883849 100644 --- a/doc/USERDOC +++ b/doc/USERDOC @@ -25,17 +25,12 @@ to the Internet), just make a local copy of the HTML files. You can get the files from the Subversion repository using the Subversion client program 'svn': - URL=https://netpbm.svn.sourceforge.net/svnroot/netpbm/userguide + URL=https://svn.code.sf.net/p/netpbm/code/userguide svn export $URL This creates a directory "userguide" in your current directory containing all the same files that are on the web site. -And a sometimes more convenient way to get those files from the Subversion -repository is to get Sourceforge's Viewvc service to make a tarball of them: - - wget http://netpbm.svn.sourceforge.net/viewvc/netpbm/userguide.tar.gz?view=tar --output-document=/tmp/userguide.tgz - An apparent alternative is just to copy the web site with something like GNU Wget. However, the Sourceforge web server has limitations on how much you can |