diff options
| author | Werner Lemberg <wl@gnu> | 1999-12-26 05:28:16 -0500 |
|---|---|---|
| committer | Werner Lemberg <wl@gnu.org> | 1999-12-26 05:28:16 -0500 |
| commit | af2d6f8e589f9fc58b98fafaad36f90302ca4b62 (patch) | |
| tree | e5aed74e162deb8f78470fb32c21030b73e06d0a /BUG-REPORT | |
| parent | 50f26cb05949bc62fa7115a63bad8e0184fd5bfd (diff) | |
| download | groff-git-af2d6f8e589f9fc58b98fafaad36f90302ca4b62.tar.gz | |
groff before CVS: release 1.141.14
Maintainer's baton passed to Werner Lemberg as of 1.12.
Diffstat (limited to 'BUG-REPORT')
| -rw-r--r-- | BUG-REPORT | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/BUG-REPORT b/BUG-REPORT index fe26601e5..b3f325c83 100644 --- a/BUG-REPORT +++ b/BUG-REPORT @@ -8,7 +8,7 @@ Please delete the text in brackets before sending it in. Please report separate bugs separately. -Send the completed form to bug-groff@prep.ai.mit.edu. +Send the completed form to bug-groff@gnu.org GROFF VERSION: [The version of groff you are using. For example, `1.05'] @@ -26,18 +26,18 @@ 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: I have them). Send them as as a shell archive +the -ms and -mm macros: we have them). Send them as a shell archive or as a uuencoded, compressed tar file. -It's easier for me if you can provide an example that doesn't depend +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 macro package that won't be possible. Also a short example is more convenient than a long one, but don't worry if you can't find a short -example. Don't say something like ``any file that X'': always send a +example. Don't say something like ``any file that X'': Always send a definite example.] COMMAND LINE: -[The command line that I should run in order to observe the bug. For +[The command line that we should run in order to observe the bug. For example, `gtroff -Tps bug.tr'. If the command line uses -ms or -mm, say whether these refer to the groff versions or the Unix versions of the macros.] @@ -46,7 +46,7 @@ DESCRIPTION OF INCORRECT BEHAVIOUR: [What goes wrong when that command line is run? For example, `gtroff gets a segmentation fault', or `The output looks bad because the bar over the x is too long and is too far over to the left.' If you get -an error message, include it here without modification: don't edit it +an error message, include it here without modification: Don't edit it to make it more readable.] SUGGESTED FIX [optional]: |