From: Fabian Keil Date: Fri, 26 Aug 2016 12:31:41 +0000 (+0000) Subject: Rebuild text files for 3.0.26 stable X-Git-Tag: v_3_0_26~9 X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff_plain;h=bc85e84cb011791a5b7f60316cea3a3e697a6b87 Rebuild text files for 3.0.26 stable --- diff --git a/AUTHORS b/AUTHORS index e402a2de..574af1f9 100644 --- a/AUTHORS +++ b/AUTHORS @@ -121,6 +121,7 @@ include (in alphabetical order): Kai Raven Roberto Ragusa Félix Rauch + Marvin Renich Chris John Riley Maynard Riley Andreas Rutkauskas diff --git a/INSTALL b/INSTALL index 4e6aac47..58ff241f 100644 --- a/INSTALL +++ b/INSTALL @@ -1,6 +1,6 @@ /********************************************************************* * - * File : $Source: /cvsroot/ijbswa/current/doc/source/install.sgml,v $ + * File : $Source: /cvsroot/ijbswa/current/INSTALL,v $ * * Purpose : INSTALL file to help with installing from source. * @@ -40,8 +40,8 @@ compiler like gcc are required. When building from a source tarball, first unpack the source: - tar xzvf privoxy-3.0.25-beta-src.tar.gz - cd privoxy-3.0.25-beta + tar xzvf privoxy-3.0.26-stable-src.tar.gz + cd privoxy-3.0.26-stable For retrieving the current CVS sources, you'll need a CVS client installed. Note that sources from CVS are typically development quality, and may not be diff --git a/README b/README index d55fb699..ae820007 100644 --- a/README +++ b/README @@ -32,9 +32,8 @@ * *********************************************************************/ -This README is included with the development version of Privoxy 3.0.25. See -https://www.privoxy.org/ for more information. The current code maturity level -is "beta", but seems stable to us :). +This README is included with Privoxy 3.0.26. See https://www.privoxy.org/ for +more information. The current code maturity level is "stable". ------------------------------------------------------------------------------- @@ -105,22 +104,16 @@ try it with FTP or other protocols for the simple reason it does not work. The actions list can be configured via the web interface accessed via http:// p.p/, as well other options. -All configuration files are subject to unannounced changes during the -development process. - ------------------------------------------------------------------------------- 5. DOCUMENTATION -There should be documentation in the 'doc' subdirectory, but it may not be -completed at this point. In particular, see the User Manual there, the FAQ, and -those interested in Privoxy development, should look at developer-manual. +There should be documentation in the 'doc' subdirectory. In particular, see the +User Manual there, the FAQ, and those interested in Privoxy development, should +look at developer-manual. -The most up to date source of information on the current development version, -may still be either comments in the source code, or the included configuration -files. The source and configuration files are all well commented. The main -configuration files are: 'config', 'default.action', and 'default.filter' in -the top-level source directory. +The source and configuration files are all well commented. The main +configuration files are: 'config', 'default.action', and 'default.filter'. Included documentation may vary according to platform and packager. All documentation is posted on https://www.privoxy.org, in case you don't have it, @@ -323,6 +316,5 @@ still be useful: https://sourceforge.net/mail/?group_id=11118. The SourceForge support trackers may be used as well, but have various technical problems that are unlikely to be fixed anytime soon. If you don't get -a timely response, please try the mailing list as well. While it's hosted at -SourceForge as well, it usually works as expected. +a timely response, please try the mailing list as well.