summaryrefslogtreecommitdiff
path: root/BUG-REPORT
diff options
context:
space:
mode:
authorG. Branden Robinson <g.branden.robinson@gmail.com>2018-11-06 08:52:22 -0500
committerG. Branden Robinson <g.branden.robinson@gmail.com>2018-11-06 09:02:09 -0500
commit81f7ba3bc0b8fa06ce64dec0eb4a12639abd35a7 (patch)
tree471dfff9e369f4194beba6a7b8636b853da6830b /BUG-REPORT
parent7908dc1dcfcb0b93fe5d35269db92702d28bc1f4 (diff)
downloadgroff-git-81f7ba3bc0b8fa06ce64dec0eb4a12639abd35a7.tar.gz
Remove instructions to file bugs via bug-groff.
Patch courtesy of Dave Kemper. His comments, massaged into GNU changelog format, follow. [The patch] also fixes a couple of trivial errors in grammar, punctuation, etc., that I spotted in the process[]. * PROJECTS: Since the context of bug-groff@gnu.org in this file is not reporting bugs, instead of changing it to point to the bug tracker, I changed the address to that of the groff discussion list. (However, I don't know whether this list is configured to accept email from nonsubscribers, so this may not be a viable change.) * README: * doc/webpage.ms: These files already recommended the bug tracker as the bug-reporting mechanism; they said using the method in the file BUG-REPORT was an alternative. As BUG-REPORT also now points to the bug tracker, I've tweaked this wording. * doc/groff.texi: The address bug-groff@gnu.org was used only once in this file, not as an address to report bugs, but as the email address for Werner Lemberg. I would take this to mean he doesn't want his actual email address in public documentation, except that it appears in many other places throughout groff source code and documentation alike. So it doesn't seem unreasonable to put it in this file as well. I will email him to confirm that this is OK. [I went ahead and removed it; we don't need an email address in the document, IMO. --GBR] * INSTALL.extra: Like README, this cited the file BUG-REPORT as an alternative mechanism. I removed this wording entirely. * BUG-REPORT: * contrib/groffer/README: * contrib/mm/README: * contrib/mm/m.tmac: * contrib/mm/mm/0.MT: * contrib/mm/mm/4.MT: * contrib/mm/mm/5.MT: * contrib/mm/mm/ms.cov: * contrib/mm/mse.tmac: * src/devices/xditview/README: Tweak wording and direct readers to Savannah bug tracker instead of bug-groff mailing list. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com>
Diffstat (limited to 'BUG-REPORT')
-rw-r--r--BUG-REPORT14
1 files changed, 7 insertions, 7 deletions
diff --git a/BUG-REPORT b/BUG-REPORT
index dcf93c8b0..0a246462d 100644
--- a/BUG-REPORT
+++ b/BUG-REPORT
@@ -19,15 +19,16 @@
Groff Bug Report
-Please read the PROBLEMS file before sending in a bug report.
+Please read the PROBLEMS file before submitting a bug report.
Please fill in all fields, even if you think they are not relevant.
-Please delete the text in brackets before sending it in.
+Please delete the text in brackets before submitting it.
Please report separate bugs separately.
-Send the completed form to bug-groff@gnu.org
+Place the completed form in a new bug report at
+http://savannah.gnu.org/bugs/?group=groff.
GROFF VERSION:
[The version of groff you are using. For example, '1.22.4']
@@ -45,8 +46,7 @@ INPUT FILES:
[Include all the files necessary to reproduce the problem that are not
part of the standard groff distribution. This includes font
description files, DESC files and macro files (with the exception of
-the -ms and -mm macros: we have them). Send them as a shell archive or
-as a uuencoded, compressed tar file.
+the -ms and -mm macros: we have them). Attach them to the bug report.
It's easier for us if you can provide an example that doesn't depend on
any macro package, but obviously if you're reporting a problem with a
@@ -69,8 +69,8 @@ error message, include it here without modification: Don't edit it to
make it more readable.]
SUGGESTED FIX [optional]:
-[If you can suggest a fix for the problem, include a context diff here.
-But don't delay sending in a bug report in the hope of finding a fix.
+[If you can suggest a fix for the problem, include a context diff here.
+But don't delay submitting a bug report in the hope of finding a fix.
Guesses about the cause of the bug are not usually helpful.]
##### Emacs settings