From 12c8dc0f934964557294fcee2ea4b5444754e032 Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Thu, 12 Mar 2020 10:39:18 +0100 Subject: [PATCH] Rebuild docs --- INSTALL | 2 +- doc/webserver/developer-manual/introduction.html | 5 ++--- doc/webserver/developer-manual/newrelease.html | 7 ++++--- doc/webserver/index.html | 2 -- doc/webserver/user-manual/installation.html | 2 +- 5 files changed, 8 insertions(+), 10 deletions(-) diff --git a/INSTALL b/INSTALL index 01b790dc..7cba5011 100644 --- a/INSTALL +++ b/INSTALL @@ -69,7 +69,7 @@ And then /etc/group, like: Some binary packages may do this for you. -Then, to build from either unpacked tarball or CVS source: +Then, to build from either unpacked tarball or Git checkout: autoheader autoconf diff --git a/doc/webserver/developer-manual/introduction.html b/doc/webserver/developer-manual/introduction.html index 3fe32d28..f029e78e 100644 --- a/doc/webserver/developer-manual/introduction.html +++ b/doc/webserver/developer-manual/introduction.html @@ -38,9 +38,8 @@

The first step is to join the privoxy-devel mailing list. You can submit your ideas or, even better, patches. Patches are best submitted to the Sourceforge tracker set up for this purpose, but can be sent to the list for review too.

-

You will also need to have a git package installed, which will entail having ssh installed as well, in order - to access the git repository. Having the GNU build tools is also going to be important (particularly, autoconf - and gmake).

+

You will also need to have a git package installed, in order to access the git repository. Having the GNU + build tools is also going to be important (particularly, autoconf and gmake).

For the time being (read, this section is under construction), you can also refer to the extensive comments in the source code. In fact, reading the code is recommended in any case.

diff --git a/doc/webserver/developer-manual/newrelease.html b/doc/webserver/developer-manual/newrelease.html index 95ac34a4..af54836d 100644 --- a/doc/webserver/developer-manual/newrelease.html +++ b/doc/webserver/developer-manual/newrelease.html @@ -203,7 +203,7 @@ for-privoxy-version=3.0.11 to be done manually.

  • -

    Tag all files in Git with the version number with "cvs tag +

    Tag all files in Git with the version number with "git tag v_X_Y_Z". Don't use vX_Y_Z, ver_X_Y_Z, v_X.Y.Z (won't work) etc.

  • @@ -227,8 +227,9 @@ for-privoxy-version=3.0.11 
      mkdir dist # delete or choose different name if it already exists
   cd dist
-  cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login
-  cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa export -r v_X_Y_Z current
    + git clone https://www.privoxy.org/git/privoxy.git + cd privoxy + git checkout v_X_Y_Z diff --git a/doc/webserver/index.html b/doc/webserver/index.html index 2f82a7c7..c8a63929 100644 --- a/doc/webserver/index.html +++ b/doc/webserver/index.html @@ -96,8 +96,6 @@

    Hosting and development is funded in part by:

    https://www.top10vpn.com

    -

    https://www.vpnranks.com/

    Become a sponsor

    diff --git a/doc/webserver/user-manual/installation.html b/doc/webserver/user-manual/installation.html index c49dca83..ec7bca81 100644 --- a/doc/webserver/user-manual/installation.html +++ b/doc/webserver/user-manual/installation.html @@ -179,7 +179,7 @@

    Some binary packages may do this for you.

    -

    Then, to build from either unpacked tarball or CVS source:

    +

    Then, to build from either unpacked tarball or Git checkout:

    -- 2.49.0