[project @ 2003-07-18 14:10:31 by cjwatson]

[debbugs.git] / html / Reporting.html.in

diff --git a/html/Reporting.html.in b/html/Reporting.html.in
index 30ced9575fdfc3c9320b346810caea8202394a6d..fbceb2fed967fe49ec9c766ef9ff907a108d568a 100644 (file)
--- a/html/Reporting.html.in
+++ b/html/Reporting.html.in
@@ -165,6 +165,12 @@ This will cause the $gBug tracking system to send a copy of your report
 to the address(es) in the <code>X-Debbugs-CC</code> line as well as to
 any mailing list.
 
+<p>Avoid sending such copies to the addresses of other $gBug reports, as
+they will be caught by the checks that prevent mail loops. There is
+relatively little point in using <code>X-Debbugs-CC</code> for this
+anyway, as the $gBug number added by that mechanism will just be
+replaced by a new one; use an ordinary <code>CC</code> header instead.
+
 <p>This feature can often be combined usefully with mailing
 <code>quiet</code> - see below.
 
@@ -225,6 +231,23 @@ only a summary).
 any forwarded message so that replies will by default be processed in
 the same way as the original report.
 
+
+<h2>Acknowledgements</h2>
+
+<p>Normally, the $gBug system will return an acknowledgement to you by
+e-mail when you report a new bug or submit additional information to an
+existing bug. If you want to suppress this acknowledgement, include an
+<code>X-Debbugs-No-Ack</code> header in your e-mail (the contents of this
+header do not matter; however, it must be in the mail header and
+<em>not</em> in the pseudo-header with the <code>Package</code> field). If
+you report a new $gBug with this header, you will need to check the web
+interface yourself to find the $gBug number.</p>
+
+<p>Note that this header will not suppress acknowledgements from the
+<code>control\@$gEmailDomain</code> mailserver, since those acknowledgements
+may contain error messages which should be read and acted upon.</p>
+
+
 <h3>$gBug reports against unknown packages</h3>
 
 <p>If the $gBug tracking system doesn't know who the maintainer of the