From 7efcdc08506f27b1441a20554817781653cae7a0 Mon Sep 17 00:00:00 2001
From: joy <>
Date: Wed, 5 Mar 2003 18:20:30 -0800
Subject: [PATCH] [project @ 2003-03-05 18:20:30 by joy] various fixes from
webwml
---
html/Reporting.html.in | 159 ++++++++++++++++++++++++++++-------------
1 file changed, 108 insertions(+), 51 deletions(-)
diff --git a/html/Reporting.html.in b/html/Reporting.html.in
index 733fd25..4e31b8b 100644
--- a/html/Reporting.html.in
+++ b/html/Reporting.html.in
@@ -9,58 +9,80 @@ $gReportingHtml = < Send mail to
- Please don't report several unrelated $gBugs - especially ones in
-different packages - in one message. Also, please don't mail your $gBug
-report to any mailing lists or recipients other than
- You should check if your $gBug report has already been filed by someone
+else before submitting it. Lists of currently outstanding $gBugs are
+available on the World Wide Web and
+elsewhere - see other documents for details.
+You can submit your comments to an existing $gBug report
+#<number> by sending e-mail to
+<number>\@$gEmailDomain If you can't seem to determine which package contains the problem,
+please send e-mail to the
+$gMaintainerEmail asking for advice.
+$gHTMLPseudoDesc
+ Lists of currently-outstanding $gBugs are available on
-the World Wide Web and elsewhere - see
-other documents for details.
+ If you'd like to send a copy of your $gBug report to additional
+recipients (such as mailing lists), you shouldn't use the usual e-mail
+headers, but a different method, described below. You need to put a pseudo-header at the start of the body of the
-message, with the See below for further requirements.
+ There is a program that was developed in Debian to help reporting
+$gBug reports, it's called
+ A $gBug report, with mail header, looks something like this:
- Send mail to
+ Of course, like with any email, you should include a clear, descriptive
+ You need to put a pseudo-header at the start
+of the body of the message. That means that the first line of the message
+body should say: Replace The second line of the message should say: Replace You need to supply a correct The pseudo-header fields should start at the very start of their lines. Please include in your report:submit\@$gEmailDomain
,
-as described below.
+Important things to note before sending
submit\@$gEmailDomain
(for details of how to do this right, see
-below).
+different packages - in a single $gBug report.
+
+Package:
and Version:
-lines giving the name and version of the package which has the $gBug.
-(The pseudo-header fields should start at the very start of their lines.)
-$gHTMLFindPackage
+Sending the bug report using an automatic bug report tool
-reportbug
.
+It will guide you through the bug reporting process step by step,
+and probably ease filing bugs that way.Example
+Sending the bug report via e-mail
-
- To: submit\@$gEmailDomain
- From: diligent\@testing.linux.org
- Subject: Hello says `goodbye'
- Package: hello
- Version: 1.3-16
+
submit\@$gEmailDomain
,
+as described below.Subject
line in your main mail header. The subject you
+give will be used as the initial $gBug title in the tracking system, so
+please try to make it informative!
+Package: <something>
+
- I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13
- and libc6 2.1.3-10.
+<something>
with the name of the package which
+has the $gBug.
+Version: <something>
-Please include in your report:
+<something>
with the version of the package.Package
line in the
+pseudo-header in order for the $gBug tracking system to deliver the message
+to the package's maintainer.
A $gBug report, with mail header, looks something like this: + +
+ To: submit\@$gEmailDomain + From: diligent\@testing.linux.org + Subject: Hello says `goodbye' + + Package: hello + Version: 1.3-16 + + When I invoke `hello' without arguments from an ordinary shell + prompt it prints `goodbye', rather than the expected `hello, world'. + Here is a transcript: + + $ hello + goodbye + $ /usr/bin/hello + goodbye + $ + + I suggest that the output string, in hello.c, be corrected. + + I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13 + and libc6 2.1.3-10. +-
Of course, like any email, you should include a clear, descriptive
-Subject
line in your main mail header. The subject you
-give will be used as the initial $gBug title in the tracking system, so
-please try to make it informative!
To assign a severity level put a
-Severity: severity
line in the pseudo-header,
-together with Package
and Version
. The
-severity levels available are described in the
-developers' documentation.
+
To assign a severity level, put a line like this one in the +pseudo-header:
+ ++Severity: <severity> ++ +
Replace <severity> with one of the available severity +levels, as described in the +developers' documentation.
patch
tag. This is not required, and the developers
will set tags on your report as and when it is appropriate.
-To set tags, put a Tags: tags
line in the
-pseudo-header together with the usual
-Package
and Version
. The tags available are
-described in the
+
To set tags, put a line like this one in the +pseudo-header:
+ ++Tags: <tags> ++ +
Replace <tags> with one or more of the available tags, +as described in the developers' documentation. -- 2.39.2