X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=html%2FReporting.html.in;h=caf81ef9a7d1351d859839d47c5b92ae414407f0;hb=refs%2Fheads%2Fbugwalker_abstraction;hp=bba28d62ef3cd536fa8106a91e815f23b6435b5a;hpb=a010fc5ee1e1d1bb419da876139231893f636497;p=debbugs.git diff --git a/html/Reporting.html.in b/html/Reporting.html.in index bba28d6..caf81ef 100644 --- a/html/Reporting.html.in +++ b/html/Reporting.html.in @@ -4,6 +4,7 @@ $gReportingHtml = < $gProject $gBugs - how to report a $gBug + @@ -11,8 +12,9 @@ $gReportingHtml = <Important things to note before sending -

Please don't report several unrelated $gBugs - especially ones in -different packages - in a single $gBug report. +

Please don't report multiple unrelated $gBugs - especially ones in +different packages - in a single $gBug report. It makes our lives much +easier if you send separate reports.

You should check if your $gBug report has already been filed by someone else before submitting it. Lists of currently outstanding $gBugs are @@ -37,12 +39,12 @@ headers, but a different method, described below.

There is a program that was developed in Debian to help reporting $gBug reports, it's called -reportbug. +reportbug. It will guide you through the bug reporting process step by step, and probably ease filing bugs that way.

Emacs users can also use the debian-bug command provided by the - + debbugs-el package. When called with M-x debian-bug, it will ask for all necessary information in a similar way to reportbug.

@@ -76,7 +78,10 @@ has the $gBug.

Version: <something> -

Replace <something> with the version of the package.

+

Replace <something> with the version of the package. +Please don't include any text here other than the version itself, as the +$gBug tracking system relies on this field to work out which releases are +affected by the bug.

You need to supply a correct Package line in the pseudo-header in order for the $gBug tracking system to deliver the message @@ -165,6 +170,12 @@ This will cause the $gBug tracking system to send a copy of your report to the address(es) in the X-Debbugs-CC line as well as to any mailing list. +

Avoid sending such copies to the addresses of other $gBug reports, as +they will be caught by the checks that prevent mail loops. There is +relatively little point in using X-Debbugs-CC for this +anyway, as the $gBug number added by that mechanism will just be +replaced by a new one; use an ordinary CC header instead. +

This feature can often be combined usefully with mailing quiet - see below. @@ -207,6 +218,16 @@ as described in the developers' documentation. Separate multiple tags with commas, spaces, or both. +

+User: <username>
+Usertags: <usertags>
+
+ +

Replace <usertags> with one or more usertags. +Separate multiple tags with commas, spaces, or both. If you specify a +username, that users tags will be set. Otherwise, the email address of +the sender will be used as the username

+

Not forwarding to the mailing list - minor $gBug reports