Rebuilt for 3.0.16 stable. Two debug lines needed manual interaction.

diff --git a/README b/README
index e918b03..72885a1 100644 (file)
--- a/README
+++ b/README
@@ -4,7 +4,7 @@
  *
  * Purpose     :  README file to give a short intro.
  *
- * Copyright   :  Written by and Copyright (C) 2001-2009 the
+ * Copyright   :  Written by and Copyright (C) 2001-2010 the
  *                Privoxy team. http://www.privoxy.org/
  *
  *                Based on the Internet Junkbuster originally written
@@ -32,9 +32,8 @@
  *
  *********************************************************************/
 
-This README is included with the development version of Privoxy 3.0.15. See
-http://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.16. See http://www.privoxy.org/ for
+more information. The current code maturity level is "stable".
 
 -------------------------------------------------------------------------------
 
@@ -54,15 +53,12 @@ Donations are welcome.
 
 1. IMPORTANT CHANGES
 
-October 2009, Privoxy 3.0.15 beta is released.
+February 2010, Privoxy 3.0.16 stable is released.
 
-This is a bugfix-release for the previous betas which introduced IPv6 support,
-improved keep-alive support and a bunch of minor improvements. See the
-"ChangeLog", and the "What's New" section and the "Upgrader's Notes" in the
-User Manual for details.
-
-Depending on the feedback it will be either followed by yet another beta
-release, or by a stable release with the same feature set.
+This is the first stable release since 3.0.12. It mainly contains bugfixes for
+the previous betas which introduced IPv6 support, improved keep-alive support
+and a bunch of minor improvements. See the "ChangeLog", and the "What's New"
+section and the "Upgrader's Notes" in the User Manual for details.
 
 -------------------------------------------------------------------------------
 
@@ -109,22 +105,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 http://www.privoxy.org, in case you don't have it,
@@ -239,12 +229,32 @@ Please be sure to provide the following information:
 
   * Any other pertinent information to help identify the problem such as config
     or log file excerpts (yes, you should have log file entries for each action
-    taken).
-
-You don't have to tell us your actual name when filing a problem report, but
-please use a nickname so we can differentiate between your messages and the
-ones entered by other "anonymous" users that may respond to your request if
-they have the same problem or already found a solution.
+    taken). To get a meaningful logfile, please make sure that the logfile
+    directive is being used and the following debug options are enabled:
+
+    debug     1 # Log the destination for each request Privoxy let through. See also debug 1024.
+    debug     2 # show each connection status
+    debug     4 # show I/O status
+    debug     8 # show header parsing
+    debug   128 # debug redirects
+    debug   256 # debug GIF de-animation
+    debug   512 # Common Log Format
+    debug  1024 # Log the destination for requests Privoxy didn't let through, and the reason why.
+    debug  4096 # Startup banner and warnings.
+    debug  8192 # Non-fatal errors
+
+    If you are having trouble with a filter, please additionally enable
+
+    debug    64 # debug regular expression filters
+
+    Note that Privoxy log files may contain sensitive information so please
+    don't submit any logfiles you didn't read first. You can mask sensitive
+    information as long as it's clear that you removed something.
+
+You don't have to tell us your actual name when filing a problem report, but if
+you don't, please use a nickname so we can differentiate between your messages
+and the ones entered by other "anonymous" users that may respond to your
+request if they have the same problem or already found a solution.
 
 Please also check the status of your request a few days after submitting it, as
 we may request additional information. If you use a SF id, you should