[Privoxy-commits] [privoxy] 15/19: Regenerate text docs for 4.3.0 UNRELEASED
User Git
git at git.privoxy.org
Thu Jun 11 08:29:19 CEST 2026
This is an automated email from the git hooks/post-receive script.
git pushed a commit to branch master
in repository privoxy.
commit 777af1b875b27508b83db6fc2237b7695de41da3
Author: Fabian Keil <fk at fabiankeil.de>
AuthorDate: Wed Jun 10 07:10:26 2026 +0200
Regenerate text docs for 4.3.0 UNRELEASED
---
AUTHORS | 1 +
INSTALL | 4 ++--
README | 21 ++++++++++++++-------
3 files changed, 17 insertions(+), 9 deletions(-)
diff --git a/AUTHORS b/AUTHORS
index 2553cf96..a2d974be 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -148,6 +148,7 @@ include (in alphabetical order):
David Mediavilla
Raphael Moll
J. Momberger
+ Dirk Mueller
Peter Müller
Mathew Murphy
Amuro Namie
diff --git a/INSTALL b/INSTALL
index 391f9e13..5a31cdd1 100644
--- a/INSTALL
+++ b/INSTALL
@@ -39,8 +39,8 @@ compiler like gcc are required.
When building from a source tarball, first unpack the source:
- tar xzvf privoxy-4.2.0-stable-src.tar.gz
- cd privoxy-4.2.0-stable
+ tar xzvf privoxy-4.3.0-beta-src.tar.gz
+ cd privoxy-4.3.0-beta
To build the development version, you can get the source code by doing:
diff --git a/README b/README
index 7a45def8..cd43d8ff 100644
--- a/README
+++ b/README
@@ -32,8 +32,9 @@
*
*********************************************************************/
-This README is included with Privoxy 4.2.0. See https://www.privoxy.org/ for
-more information. The current code maturity level is "stable".
+This README is included with the development version of Privoxy 4.3.0. See
+https://www.privoxy.org/ for more information. The current code maturity level
+is "UNRELEASED", but seems stable to us :).
-------------------------------------------------------------------------------
@@ -104,16 +105,22 @@ 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. 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, 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.
-The source and configuration files are all well commented. The main
-configuration files are: 'config', 'default.action', and 'default.filter'.
+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.
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,
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
More information about the Privoxy-commits
mailing list