head	1.1;
branch	1.1.1;
access;
symbols
	RELENG_8_4:1.1.1.3.0.56
	RELENG_9_1_0_RELEASE:1.1.1.3
	RELENG_9_1:1.1.1.3.0.54
	RELENG_9_1_BP:1.1.1.3
	RELENG_8_3_0_RELEASE:1.1.1.3
	RELENG_8_3:1.1.1.3.0.52
	RELENG_8_3_BP:1.1.1.3
	RELENG_9_0_0_RELEASE:1.1.1.3
	RELENG_9_0:1.1.1.3.0.50
	RELENG_9_0_BP:1.1.1.3
	RELENG_9:1.1.1.3.0.48
	RELENG_9_BP:1.1.1.3
	RELENG_7_4_0_RELEASE:1.1.1.3
	RELENG_8_2_0_RELEASE:1.1.1.3
	RELENG_7_4:1.1.1.3.0.46
	RELENG_7_4_BP:1.1.1.3
	RELENG_8_2:1.1.1.3.0.44
	RELENG_8_2_BP:1.1.1.3
	RELENG_8_1_0_RELEASE:1.1.1.3
	RELENG_8_1:1.1.1.3.0.42
	RELENG_8_1_BP:1.1.1.3
	RELENG_7_3_0_RELEASE:1.1.1.3
	RELENG_7_3:1.1.1.3.0.40
	RELENG_7_3_BP:1.1.1.3
	RELENG_8_0_0_RELEASE:1.1.1.3
	RELENG_8_0:1.1.1.3.0.38
	RELENG_8_0_BP:1.1.1.3
	RELENG_8:1.1.1.3.0.36
	RELENG_8_BP:1.1.1.3
	RELENG_7_2_0_RELEASE:1.1.1.3
	RELENG_7_2:1.1.1.3.0.34
	RELENG_7_2_BP:1.1.1.3
	RELENG_7_1_0_RELEASE:1.1.1.3
	RELENG_6_4_0_RELEASE:1.1.1.3
	RELENG_7_1:1.1.1.3.0.32
	RELENG_7_1_BP:1.1.1.3
	RELENG_6_4:1.1.1.3.0.30
	RELENG_6_4_BP:1.1.1.3
	RELENG_7_0_0_RELEASE:1.1.1.3
	RELENG_6_3_0_RELEASE:1.1.1.3
	RELENG_7_0:1.1.1.3.0.28
	RELENG_7_0_BP:1.1.1.3
	RELENG_6_3:1.1.1.3.0.26
	RELENG_6_3_BP:1.1.1.3
	RELENG_7:1.1.1.3.0.24
	RELENG_7_BP:1.1.1.3
	RELENG_6_2_0_RELEASE:1.1.1.3
	RELENG_6_2:1.1.1.3.0.22
	RELENG_6_2_BP:1.1.1.3
	RELENG_5_5_0_RELEASE:1.1.1.3
	RELENG_5_5:1.1.1.3.0.20
	RELENG_5_5_BP:1.1.1.3
	RELENG_6_1_0_RELEASE:1.1.1.3
	RELENG_6_1:1.1.1.3.0.18
	RELENG_6_1_BP:1.1.1.3
	RELENG_6_0_0_RELEASE:1.1.1.3
	v1_19_2:1.1.1.3
	RELENG_6_0:1.1.1.3.0.16
	RELENG_6_0_BP:1.1.1.3
	RELENG_6:1.1.1.3.0.14
	RELENG_6_BP:1.1.1.3
	RELENG_5_4_0_RELEASE:1.1.1.3
	RELENG_5_4:1.1.1.3.0.12
	RELENG_5_4_BP:1.1.1.3
	RELENG_4_11_0_RELEASE:1.1.1.2.2.1
	RELENG_4_11:1.1.1.2.2.1.0.18
	RELENG_4_11_BP:1.1.1.2.2.1
	RELENG_5_3_0_RELEASE:1.1.1.3
	RELENG_5_3:1.1.1.3.0.10
	RELENG_5_3_BP:1.1.1.3
	RELENG_5:1.1.1.3.0.8
	RELENG_5_BP:1.1.1.3
	RELENG_4_10_0_RELEASE:1.1.1.2.2.1
	RELENG_4_10:1.1.1.2.2.1.0.16
	RELENG_4_10_BP:1.1.1.2.2.1
	RELENG_5_2_1_RELEASE:1.1.1.3
	RELENG_5_2_0_RELEASE:1.1.1.3
	RELENG_5_2:1.1.1.3.0.6
	RELENG_5_2_BP:1.1.1.3
	RELENG_4_9_0_RELEASE:1.1.1.2.2.1
	RELENG_4_9:1.1.1.2.2.1.0.14
	RELENG_4_9_BP:1.1.1.2.2.1
	RELENG_5_1_0_RELEASE:1.1.1.3
	RELENG_5_1:1.1.1.3.0.4
	RELENG_5_1_BP:1.1.1.3
	v1_19:1.1.1.3
	RELENG_4_8_0_RELEASE:1.1.1.2.2.1
	RELENG_4_8:1.1.1.2.2.1.0.12
	RELENG_4_8_BP:1.1.1.2.2.1
	RELENG_5_0_0_RELEASE:1.1.1.3
	RELENG_5_0:1.1.1.3.0.2
	RELENG_5_0_BP:1.1.1.3
	v1_18_1:1.1.1.3
	RELENG_4_7_0_RELEASE:1.1.1.2.2.1
	RELENG_4_7:1.1.1.2.2.1.0.10
	RELENG_4_7_BP:1.1.1.2.2.1
	RELENG_4_6_2_RELEASE:1.1.1.2.2.1
	RELENG_4_6_1_RELEASE:1.1.1.2.2.1
	RELENG_4_6_0_RELEASE:1.1.1.2.2.1
	RELENG_4_6:1.1.1.2.2.1.0.8
	RELENG_4_6_BP:1.1.1.2.2.1
	RELENG_4_5_0_RELEASE:1.1.1.2.2.1
	RELENG_4_5:1.1.1.2.2.1.0.6
	RELENG_4_5_BP:1.1.1.2.2.1
	RELENG_4_4_0_RELEASE:1.1.1.2.2.1
	RELENG_4_4:1.1.1.2.2.1.0.4
	RELENG_4_4_BP:1.1.1.2.2.1
	v1_17_2:1.1.1.3
	RELENG_4_3_0_RELEASE:1.1.1.2.2.1
	RELENG_4_3:1.1.1.2.2.1.0.2
	RELENG_4_3_BP:1.1.1.2.2.1
	v1_17:1.1.1.3
	v1_16_1:1.1.1.3
	RELENG_4_2_0_RELEASE:1.1.1.2
	RELENG_4_1_1_RELEASE:1.1.1.2
	PRE_SMPNG:1.1.1.2
	RELENG_4_1_0_RELEASE:1.1.1.2
	RELENG_3_5_0_RELEASE:1.1.1.1.4.1
	RELENG_4_0_0_RELEASE:1.1.1.2
	RELENG_4:1.1.1.2.0.2
	RELENG_4_BP:1.1.1.2
	v1_15:1.1.1.2
	RELENG_3_4_0_RELEASE:1.1.1.1
	RELENG_3_3_0_RELEASE:1.1.1.1
	RELENG_3_2_PAO:1.1.1.1.0.6
	RELENG_3_2_PAO_BP:1.1.1.1
	RELENG_3_2_0_RELEASE:1.1.1.1
	v1_11:1.1.1.1
	RELENG_3_1_0_RELEASE:1.1.1.1
	RELENG_3:1.1.1.1.0.4
	RELENG_3_BP:1.1.1.1
	RELENG_2_2_8_RELEASE:1.1.1.1
	RELENG_3_0_0_RELEASE:1.1.1.1
	RELENG_2_2_7_RELEASE:1.1.1.1
	RELENG_2_2_6_RELEASE:1.1.1.1
	RELENG_2_2_5_RELEASE:1.1.1.1
	RELENG_2_2_2_RELEASE:1.1.1.1
	RELENG_2_2_1_RELEASE:1.1.1.1
	RELENG_2_2_0_RELEASE:1.1.1.1
	RELENG_2_2:1.1.1.1.0.2
	RELENG_2_2_BP:1.1.1.1
	v1_10:1.1.1.1
	FSF:1.1.1;
locks; strict;
comment	@# @;


1.1
date	96.09.07.16.17.57;	author pst;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	96.09.07.16.17.57;	author pst;	state Exp;
branches
	1.1.1.1.4.1;
next	1.1.1.2;

1.1.1.2
date	2000.01.12.09.48.04;	author asmodai;	state Exp;
branches
	1.1.1.2.2.1;
next	1.1.1.3;

1.1.1.3
date	2000.12.05.18.49.19;	author ru;	state Exp;
branches
	1.1.1.3.56.1;
next	;

1.1.1.1.4.1
date	2000.03.09.20.05.59;	author asmodai;	state Exp;
branches;
next	;

1.1.1.2.2.1
date	2000.12.07.09.48.10;	author ru;	state Exp;
branches;
next	;

1.1.1.3.56.1
date	2000.12.05.18.49.19;	author svnexp;	state dead;
branches;
next	1.1.1.3.56.2;

1.1.1.3.56.2
date	2013.03.28.13.01.12;	author svnexp;	state Exp;
branches;
next	;


desc
@@


1.1
log
@Initial revision
@
text
@			   Groff Bug Report

Please read the PROBLEMS file before sending in 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 report separate bugs separately.

Send the completed form to bug-groff@@prep.ai.mit.edu.

GROFF VERSION:
[The version of groff you are using.  For example, `1.05']

MACHINE:
[The machine you are using.  For example, `Sun SPARCstation 2']

OS:
[The operating system you are using.  For example, `SunOS 4.1.1']

COMPILER:
[The compiler you are used to compile groff. For example, `g++ 1.40.3']

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
or as a uuencoded, compressed tar file.

It's easier for me 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
definite example.]

COMMAND LINE:
[The command line that I 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.]

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
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.  Guesses about the cause of the bug are not usually helpful.]
@


1.1.1.1
log
@Virgin import of FSF groff v1.10
@
text
@@


1.1.1.1.4.1
log
@MFC: groff 1.15
@
text
@d11 1
a11 1
Send the completed form to bug-groff@@gnu.org
d29 1
a29 1
the -ms and -mm macros: we have them).  Send them as a shell archive
d32 1
a32 1
It's easier for us if you can provide an example that doesn't depend
d36 1
a36 1
example.  Don't say something like ``any file that X'': Always send a
d40 1
a40 1
[The command line that we should run in order to observe the bug.  For
d49 1
a49 1
an error message, include it here without modification: Don't edit it
@


1.1.1.2
log
@Virgin import of FSF groff v1.15
@
text
@d11 1
a11 1
Send the completed form to bug-groff@@gnu.org
d29 1
a29 1
the -ms and -mm macros: we have them).  Send them as a shell archive
d32 1
a32 1
It's easier for us if you can provide an example that doesn't depend
d36 1
a36 1
example.  Don't say something like ``any file that X'': Always send a
d40 1
a40 1
[The command line that we should run in order to observe the bug.  For
d49 1
a49 1
an error message, include it here without modification: Don't edit it
@


1.1.1.2.2.1
log
@MFC: Upgrade to Groff 1.16.1.
@
text
@d23 1
a23 1
[The compiler you are used to compile groff.  For example, `g++ 1.40.3']
d29 2
a30 2
the -ms and -mm macros: we have them).  Send them as a shell archive or
as a uuencoded, compressed tar file.
d32 3
a34 3
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
d48 3
a50 3
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 to
make it more readable.]
d53 3
a55 3
[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. 
Guesses about the cause of the bug are not usually helpful.]
@


1.1.1.3
log
@Virgin import of FSF groff v1.16.1
@
text
@d23 1
a23 1
[The compiler you are used to compile groff.  For example, `g++ 1.40.3']
d29 2
a30 2
the -ms and -mm macros: we have them).  Send them as a shell archive or
as a uuencoded, compressed tar file.
d32 3
a34 3
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
d48 3
a50 3
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 to
make it more readable.]
d53 3
a55 3
[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. 
Guesses about the cause of the bug are not usually helpful.]
@


1.1.1.3.56.1
log
@file BUG-REPORT was added on branch RELENG_8_4 on 2013-03-28 13:01:12 +0000
@
text
@d1 55
@


1.1.1.3.56.2
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/248810
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@a0 55
			   Groff Bug Report

Please read the PROBLEMS file before sending in 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 report separate bugs separately.

Send the completed form to bug-groff@@gnu.org

GROFF VERSION:
[The version of groff you are using.  For example, `1.05']

MACHINE:
[The machine you are using.  For example, `Sun SPARCstation 2']

OS:
[The operating system you are using.  For example, `SunOS 4.1.1']

COMPILER:
[The compiler you are used to compile groff.  For example, `g++ 1.40.3']

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.

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
definite example.]

COMMAND LINE:
[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.]

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 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. 
Guesses about the cause of the bug are not usually helpful.]
@


