Package: bugs.debian.org
Severity: normal

The Assigning tags section from http://www.debian.org/Bugs/Reporting.en.html#pseudoheader contains:

You can set tags on a bug as you are reporting it. For example, if you are including a patch with your bug report, you may wish to set the |patch| tag. This is not required, however, and the developers will set tags on your report as and when it is appropriate.

To set tags, put a line like this one in the pseudo-header <http://www.debian.org/Bugs/Reporting.en.html#pseudoheader>:

Tags:<tags>

Replace <tags> with one or more of the available tags, as described in the advanced documentation <http://www.debian.org/Bugs/Developer#tags>. 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 user's tags will be set. Otherwise, the e-mail address of the sender will be used as the username.

Forwarded:f...@example.com

will mark the newly submitted bug as forwarded to f...@example.com. See Recording that you have passed on a bug report <http://www.debian.org/Bugs/Developer#forward> in the developers' documentation for details.

Owner:f...@example.com

will indicate that f...@example.com is now responsible for fixing this bug. See Changing bug ownership <http://www.debian.org/Bugs/Developer#owner> in the developers' documentation for details.

Source:foopackage

the equivalent of |Package:| for bugs present in the source package of foopackage; for most bugs in most packages you don't want to use this option.

Finally, if your MUA doesn't allow you to edit the headers, you can set the various |X-Debbugs-| headers in the pseudo-headers <http://www.debian.org/Bugs/Reporting.en.html#pseudoheader>.


The start of the section is indeed about tags, but the second half isn't. The unrelated part could either be split in a few new subsections (Forwarding, Ownership, etc.) or be separated from the rest by creating an "Other" subsection.

Reply via email to