* fix the link class

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

diff --git a/html/Developer.html.in b/html/Developer.html.in
index ab4ea80fca72ff5933b53a794c4a2f70bba015c0..d876d91dbaa9ceec1cd07922b6b1ff0d01cb7b10 100644 (file)
--- a/html/Developer.html.in
+++ b/html/Developer.html.in
@@ -38,7 +38,7 @@ included it in the <code>Reply-To</code>.
 
 <p>Where applicable, please supply a <code>Version</code> line in the
 <a href="Reporting.html#pseudoheader">pseudo-header</a> of your message when
-closing a bug, so that the $gBug tracking system knows which releases of the
+closing a $gBug, so that the $gBug tracking system knows which releases of the
 package contain the fix.</p>
 
 <p>`Done' messages are automatically forwarded to the <code>$gDoneList</code>
@@ -123,14 +123,19 @@ they should note this in the $gBug tracking system as follows:
 
 <p>Make sure that the <code>To</code> field of your message to the author
 has only the author(s) address(es) in it; put both the person who
-reported the $gBug and
-<var>nnn</var><code>-forwarded\@$gEmailDomain</code> in the
+reported the $gBug, 
+<var>nnn</var><code>-forwarded\@$gEmailDomain</code> and
+<var>nnn</var><code>\@$gEmailDomain</code> in the
 <code>CC</code> field.
 
 <p>Ask the author to preserve the <code>CC</code> to
-<var>nnn</var><code>-forwarded\@$gEmailDomain</code> when they reply, so that
-the $gBug tracking system will file their reply with the original
-report.
+<var>nnn</var><code>-forwarded\@$gEmailDomain</code>
+and <var>nnn</var><code>\@$gEmailDomain</code> when they reply, so
+that the $gBug tracking system will file their reply with the original
+report. These messages are only filed and are not sent on; to send a
+message as normal, send them
+to <var>nnn</var><code>\@$gEmailDomain</code> as well.</p>
+
 
 <p>When the $gBug tracking system gets a message at
 <var>nnn</var><code>-forwarded</code> it will mark the relevant $gBug as
@@ -169,8 +174,8 @@ $gBadMaintHtml
 <p>It is possible to reassign $gBug reports to other packages, to reopen
 erroneously-closed ones, to modify the information saying to where, if
 anywhere, a $gBug report has been forwarded, to change the severities
-and titles of reports, to set the ownership of bugs, to merge and unmerge
-$gBug reports, and to record the versions of packages in which bugs were
+and titles of reports, to set the ownership of $gBugs, to merge and unmerge
+$gBug reports, and to record the versions of packages in which $gBugs were
 found and in which they were fixed.  This is done by sending mail to
 <code>control\@$gEmailDomain</code>.