X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=README;h=72885a1dfd58976e86928ba278cd74882f777184;hb=70b9ed04dec24ef32a00a14dbe2a1556275e9bd3;hp=931b4579ab9d17604ef8585b9322641b242e6fcf;hpb=a54cb7d58d243d60158fe414d205d658e9e1a7a2;p=privoxy.git

diff --git a/README b/README
index 931b4579..72885a1d 100644
--- 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 SourceForge
+ * Copyright   :  Written by and Copyright (C) 2001-2010 the
  *                Privoxy team. http://www.privoxy.org/
  *
  *                Based on the Internet Junkbuster originally written
@@ -32,7 +32,7 @@
  *
  *********************************************************************/
 
-This README is included with Privoxy 3.0.12. See http://www.privoxy.org/ for
+This README is included with Privoxy 3.0.16. See http://www.privoxy.org/ for
 more information. The current code maturity level is "stable".
 
 -------------------------------------------------------------------------------
@@ -46,32 +46,20 @@ networks.
 
 Privoxy is Free Software and licensed under the GPL2.
 
+Privoxy is an associated project of Software in the Public Interest (SPI).
+Donations are welcome.
+
 -------------------------------------------------------------------------------
 
 1. IMPORTANT CHANGES
 
-March 2009, Privoxy 3.0.12 is released.
+February 2010, Privoxy 3.0.16 stable is released.
 
-This is primarily a bug fix release. See the "ChangeLog", and the "What's New"
+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.
 
-February 2009, Privoxy 3.0.11 is released.
-
-As usual there are changes that effect the configuration. See the "ChangeLog",
-and the "What's New" section and the "Upgrader's Notes" in the User Manual for
-details and specifics.
-
-This is a stable release, and marks a departure for Privoxy development.
-
-Previously, odd numbered releases were considered beta versions and were only
-released at the end of the development cycle when the code was already believed
-to be stable. Usually it was, so the stable release contained pretty much the
-same code, but got a higher version number. In the future we intend to release
-several snapshots between stable releases. There will probably still be about
-two stable releases per year, but hopefully about six snapshots instead of the
-two betas we have now. The intentions is to make testing without CVS access
-easier.
-
 -------------------------------------------------------------------------------
 
 2. INSTALL
@@ -93,8 +81,6 @@ If no config_file is specified on the command line, Privoxy will look for a
 file named 'config' in the current directory (except Win32 which will look for
 'config.txt'). If no config_file is found, Privoxy will fail to start.
 
-Or for Red Hat and Fedora based distributions: /etc/rc.d/init.d/privoxy start
-
 Or Debian and Ubuntu: /etc/init.d/privoxy start
 
 -------------------------------------------------------------------------------
@@ -243,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