summaryrefslogtreecommitdiff
path: root/README
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 /README
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 'README')
-rw-r--r--README16
1 files changed, 7 insertions, 9 deletions
diff --git a/README b/README
index 7d255e048..e1e24df44 100644
--- a/README
+++ b/README
@@ -89,18 +89,16 @@ page at
https://savannah.gnu.org/projects/groff
-Alternatively, but less preferable, you may use the form in the file
-`BUG-REPORT'; the idea of this is to make sure that FSF has all the
-information it needs to fix the bug. At the very least, read the
-`BUG-REPORT' form and make sure that you supply all the information
-that it asks for. Even if you are not sure that something is a bug,
-report it using `BUG-REPORT': this enables us to determine whether it
-really is a bug or not.
+You may use the form in the file `BUG-REPORT'; the idea of this is to
+make sure that FSF has all the information it needs to fix the bug.
+At the very least, read the `BUG-REPORT' form and make sure that you
+supply all the information that it asks for. Even if you are not sure
+that something is a bug, report it: this enables us to determine whether
+it really is a bug.
Three mailing lists are available:
- bug-groff@gnu.org for reporting bugs and following bug
- reports
+ bug-groff@gnu.org for following bug reports
groff@gnu.org for general discussion of groff
groff-commit@gnu.org a read-only list to follow commits
to the git repository