From: Fabian Keil
Date: Wed, 17 Aug 2011 10:37:48 +0000 (+0000)
Subject: Rebuild user-manual, developer-manual and faq.
X-Git-Tag: v_3_0_18~134
X-Git-Url: http://www.privoxy.org/gitweb/@default-cgi@/faq/%22https:/@default-cgi@show-url-info?a=commitdiff_plain;h=5700aead3098beb0cc5a02bc0034a0d4194774a6;p=privoxy.git
Rebuild user-manual, developer-manual and faq.
Looks like the code status UNRELEASED isn't properly dealt with everywhere,
but as this build is not going to get released, I think we can live with
it for now.
Also ampersands in URLs weren't properly escaped, but hopefully
none of the broken links slipped into this commit. This needs to
be addressed before the next release anyway.
---
diff --git a/doc/webserver/developer-manual/contact.html b/doc/webserver/developer-manual/contact.html
index 763e6713..e87e6046 100644
--- a/doc/webserver/developer-manual/contact.html
+++ b/doc/webserver/developer-manual/contact.html
@@ -119,6 +119,13 @@ TARGET="_top"
> Please don't sent private support requests to individual Privoxy
developers, either use the mailing lists or the support trackers.
If you have to contact a Privoxy developer directly for other reasons,
+ please send a real mail and do not bother with SourceForge's messaging
+ system. Answers to SourceForge messages are usually bounced by SourceForge's
+ mail server in which case the developer wasted time writing a response you
+ don't get. From your point of view it will look like your message has
+ been completely ignored, so this is frustrating for all parties involved.
Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
addresses have to be accepted manually by a moderator. This may cause a
delay of several days and if you use a subject that doesn't clearly
@@ -553,4 +560,4 @@ VALIGN="top"
>