From 560e9a67ad74dca45daf4a4ec51edf55189ddf88 Mon Sep 17 00:00:00 2001 From: gdr-ftp Date: Fri, 19 Jun 1998 23:35:07 +0000 Subject: [PATCH] bugs.html: Explain how to submit followups to a given PR (problem report) using the email interface. --- doc/refs/bugs.html | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) 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. +

+ +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 Report Followups subsection under Email Access, below.

Bug Reports -- Email Access

+

Initial Reports

+ If you prefer to send your bug reports via regular email, you can send them to gno-bugs@trenco.gno.org. @@ -102,4 +109,20 @@ the reporting system. If your bug report contains proprietary information, you should send it to gno-bugs-admin@trenco.gno.org -

\ No newline at end of file +

+ +

Report Followups

+ +If you wish to use the email interface to enter followup text on a +particular, you can do it by emailing your message to +gno-bugs@trenco.gno.org, +provided that your subject line follows a particular format. +Specifically, the subject line must contain the text +(PR#nn), where nn 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. +

+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. +