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>
This commit is contained in:
G. Branden Robinson 2018-11-06 08:52:22 -05:00
parent 7908dc1dcf
commit 81f7ba3bc0
15 changed files with 45 additions and 42 deletions

View File

@ -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

View File

@ -144,9 +144,6 @@ tracker at
https://savannah.gnu.org/projects/groff
Alternative, but less preferable, you may send a bug report using the
form in the file BUG-REPORT.
##### Emacs settings
Local Variables:
mode: text

View File

@ -40,7 +40,7 @@ Here are some things that would be useful additions to groff:
(like pm and -mpm)
If you want to work on one of these, you should probably post to
gnu.groff.bug (or send email to bug-groff@gnu.org) to see if anyone else
gnu.groff.bug (or send email to groff@gnu.org) to see if anyone else
has gotten there first.

16
README
View File

@ -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

View File

@ -55,7 +55,7 @@ the 'tty' text mode with a pager is tried by default.
File access
The Perl version of groffer now use umask of 077. This is a very
The Perl version of groffer now uses a umask of 077. This is a very
strict security issue. It allows only access of the temporary files
by the file owner.
@ -67,17 +67,20 @@ requests based on the man path and compressed files. That's more than
'groff' does.
Mailing lists
Reporting bugs
For reporting bugs of 'groffer', groff's free mailing list
<bug-groff@gnu.org> can be used.
For reporting bugs of 'groffer', groff's bug-tracking tool at
http://savannah.gnu.org/bugs/?group=groff can be used.
For a general discussion, the mailing list <groff@gnu.org> is more
Mailing list
For a general discussion, the mailing list <groff@gnu.org> is
useful, but one has to subscribe to this list at
http://lists.gnu.org/mailman/listinfo/groff.
See the 'README' file in the top directory of the 'groff' source
package for more details on these mailing lists.
package for more details on this mailing list.
####### License

View File

@ -9,8 +9,9 @@ This is mgm, a macro package for groff.
It is supposed to be compatible with the DWB mm macros,
and has several extensions.
Send bug reports to bug-groff@gnu.org with a description of the problem
and a sample of text which reproduces the error.
Submit bug reports at http://savannah.gnu.org/bugs/?group=groff with a
description of the problem and a sample of text which reproduces the
error.
Don't forget to mention the version of mgm (look in the beginning
of m.tmac) and the version of groff.

View File

@ -16,7 +16,8 @@ for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Please send bug reports with examples to bug-groff@gnu.org.
Please submit bug reports with examples at
http://savannah.gnu.org/bugs/?group=groff.
Naming convention stolen from mgs.
Local names module*name

View File

@ -17,7 +17,8 @@ for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Please send bug reports with examples to bug-groff@gnu.org.
Please submit bug reports with examples at
http://savannah.gnu.org/bugs/?group=groff.
..
.
.\"------------

View File

@ -17,7 +17,8 @@ for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Please send bug reports with examples to bug-groff@gnu.org.
Please submit bug reports with examples at
http://savannah.gnu.org/bugs/?group=groff.
..
.
.\"------------

View File

@ -17,7 +17,8 @@ for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Please send bug reports with examples to bug-groff@gnu.org.
Please submit bug reports with examples at
http://savannah.gnu.org/bugs/?group=groff.
..
.
.\"------------

View File

@ -17,7 +17,8 @@ for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Please send bug reports with examples to bug-groff@gnu.org.
Please submit bug reports with examples at
http://savannah.gnu.org/bugs/?group=groff.
..
.
.\"------------

View File

@ -16,7 +16,8 @@ for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Please send bug reports with examples to bug-groff@gnu.org.
Please submit bug reports with examples at
http://savannah.gnu.org/bugs/?group=groff.
..
.
.\"

View File

@ -547,7 +547,7 @@ developing GNU and promoting software freedom.''
@subtitle Edition 1.22.4
@subtitle Autumn 2018
@author by Trent A.@tie{}Fisher
@author and Werner Lemberg (@email{bug-groff@@gnu.org})
@author and Werner Lemberg
@page
@vskip 0pt plus 1filll

View File

@ -220,14 +220,12 @@ Bug reports
Please report bugs using the project's
.URL https://\:savannah.gnu.org/\:projects/\:groff "bug tracker" .
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.
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.
Even if you are not sure that something is a bug, report it:
this enables us to determine whether it really is a bug.
.
.
.SH

View File

@ -10,4 +10,4 @@ xditview is copyrighted by MIT under the usual X terms (see
gxditview.man); the changes to that which come along with the groff package
are in the public domain.
Please report bugs to bug-groff@gnu.org.
Please report bugs at http://savannah.gnu.org/bugs/?group=groff.