diff --git a/doc/refs/bugs.html b/doc/refs/bugs.html
index d1008e0..7b3c956 100644
--- a/doc/refs/bugs.html
+++ b/doc/refs/bugs.html
@@ -45,10 +45,17 @@ Note that this reporting system is accessible from Lynx, but is more
 readable using a graphical browser.  This is unfortunate, but fixing
 this problem will require modifications to the bug tracking software
 itself.  This will be addressed when time permits.
+<p>
+
+While the web interface allows replies and followups to existing reports,
+it is also possible to send replies and followups using regular email.
+See the <b>Report Followups</b> subsection under <b>Email Access</b>, below.
 
 <hr>
 <H3>Bug Reports -- Email Access</H3>
 
+<H4>Initial Reports</H4>
+
 If you prefer to send your bug reports via regular email, you can 
 send them to 
 <A HREF="mailto:gno-bugs@trenco.gno.org">gno-bugs@trenco.gno.org</A>.
@@ -102,4 +109,20 @@ the reporting system.  If your bug report contains proprietary information,
 you should send it to
 <A HREF="mailto:gno-bugs-admin@trenco.gno.org">
 gno-bugs-admin@trenco.gno.org</A>
-<p>
\ No newline at end of file
+<p>
+
+<H4>Report Followups</H4>
+
+If you wish to use the email interface to enter followup text on a
+particular, you can do it by emailing your message to
+<b>gno-bugs@trenco.gno.org</b>, 
+<em>provided that your subject line follows a particular format</em>.
+Specifically, the subject line must contain the text
+<b>(PR#</b><em>nn</em><b>)</b>, where <em>nn</em> is the problem report
+number.  This string must not contain any whitespace or other characters,
+except as shown.  The parenthesis are part of the string.
+<p>
+The subject line may contain other text, but the above is required
+for the message to be recognised as a followup rather than a new problem
+report.
+<p>