[Gpg4win-commits] r343 - trunk/doc/website

[scm-commit@wald.intevation.org]

Author: jan
Date: 2006-08-06 00:34:53 +0200 (Sun, 06 Aug 2006)
New Revision: 343

Modified:
   trunk/doc/website/reporting-bugs.htm4
Log:
Removed expert elements. Its just too dangerous
regarding cleartext passwords.


Modified: trunk/doc/website/reporting-bugs.htm4
===================================================================
--- trunk/doc/website/reporting-bugs.htm4	2006-08-04 19:49:23 UTC (rev 342)
+++ trunk/doc/website/reporting-bugs.htm4	2006-08-05 22:34:53 UTC (rev 343)
@@ -96,29 +96,8 @@
 <h3>Creating debug log information</h3>
 
 <p>
-GPGME is a middle layer between GnuPG and all
-Gpg4win modules except for GPGee.
-</p>
-
-<p>
-To obtain detailed debugging information, you
-must enter something like this on the DOS prompt:
-</p>
-
-<pre>
-set GPGME_DEBUG=5;c:\temp\gpgme.log
-"c:\Program Files\Microsoft Office\OFFICE11\OUTLOOK.EXE"
-</pre>
-
-<p>
-In this case the communication between GPGol and Outlook
-will be logged into the file \tmp\gpgme.log.
-</p>
-
-<p>
 GPGol has an extra debug options which helps to understand the
-internal communication between Outlook and GPGol; this debugging
-feature is often more important than the above noted gpgme logging.
+internal communication between Outlook and GPGol.
 To enable it, go to the GnuPG tab in Outlook's option page, click on
 the "Advanced" button and enter
 </p>
@@ -132,12 +111,6 @@
 </p>
 
 <p>
-<em>Please note</em> that you should search for passwords
-in these files and replace them by XXX before submitting the log
-file(s) to a bug tracker.
-</p>
-
-<p>
 If you feel able to, just send a excerpt with the relevant
 information.
 </p>