mention d-i bugs
|Deletions are marked like this.||Additions are marked like this.|
|Line 10:||Line 10:|
|* User: ports mailinglist||* User: ports mailing list|
|Line 15:||Line 15:|
|The port mailinglist name is usually '`email@example.com`' or '`firstname.lastname@example.org`'. Examples of the latter include:||The port mailing list name is usually '`email@example.com`' or '`firstname.lastname@example.org`'. Examples of the latter include:|
|Line 23:||Line 23:|
|* ppc64: email@example.com|
These tags are meant to signal that particular bugs are architecture-specific. Maintainers are encouraged to mark any and all architecture-specific bugs with the below tag, whether or not a fix is available; this will allow porters to get a better overview of the state of their port.
When filing architecture-specific bugs, please also ensure that you add an X-Debbugs-CC field listing each of the appropriate porter lists.
The generic format of these tags is:
- User: ports mailing list
- Usertags: port name
The port mailing list name is usually 'firstname.lastname@example.org' or 'email@example.com'. Examples of the latter include:
There are some exceptions to these rules:
x32: firstname.lastname@example.org, but the list does not exist yet.
For both kfreebsd-i386 and kfreebsd-amd64 (aka GNU/kFreeBSD) please add the usertag kfreebsd in addition to the architecture names.
For x32 the list does not exist so you should X-Debbugs-CC: email@example.com instead.