1228
Comment: x32
|
1677
This is a field in the header or pseudo-header
|
Deletions are marked like this. | Additions are marked like this. |
Line 2: | Line 2: |
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. | 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. |
Line 6: | Line 6: |
* user: ports mailinglist * usertag: port name |
* User: ports mailinglist * Usertags: port name |
Line 11: | Line 11: |
The port mailinglist name is usually '`debian-$architecture@lists.debian.org`'. The exceptions to this rule are as follows: | The port mailinglist name is usually '`debian-$architecture@lists.debian.org`' or '`debian-$archfamily@lists.debian.org`'. Examples of the latter include: |
Line 14: | Line 14: |
* armhf: debian-arm@lists.debian.org * arm64: debian-arm@lists.debian.org |
|
Line 15: | Line 17: |
* mips64el: debian-mips@lists.debian.org | |
Line 16: | Line 19: |
* sh: debian-superh@mlists.debian.org x32 has no mailinglist at debian-x32@lists.debian.org, yet it uses that tag. |
* ppc64el: debian-powerpc@lists.debian.org * riscv64: debian-riscv@lists.debian.org * sh: debian-superh@lists.debian.org * sh4: debian-superh@lists.debian.org * s390x: debian-s390@lists.debian.org |
Line 22: | Line 27: |
For both kfreebsd-i386 and kfreebsd-amd64 (aka GNU/kFreeBSD) please use | There are some exceptions to these rules: |
Line 24: | Line 29: |
* user: debian-bsd@lists.debian.org * usertag: kfreebsd |
* m86k: debian-68k@lists.debian.org * x32: debian-x32@lists.debian.org * kfreebsd-i386: debian-bsd@lists.debian.org * kfreebsd-amd64: debian-bsd@lists.debian.org |
Line 29: | Line 36: |
Additionally, the m68k port's mailinglist is officially called debian-68k@lists.debian.org, but has an alias 'debian-m68k@lists.debian.org'. In the interest of consistency, maintainers should use the m68k name of the list rather than the official name. | 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: debian-amd64@lists.debian.org instead. |
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 mailinglist
- Usertags: port name
The port mailinglist name is usually 'debian-$architecture@lists.debian.org' or 'debian-$archfamily@lists.debian.org'. Examples of the latter include:
armel: debian-arm@lists.debian.org
armhf: debian-arm@lists.debian.org
arm64: debian-arm@lists.debian.org
hurd-i386: debian-hurd@lists.debian.org
mips64el: debian-mips@lists.debian.org
mipsel: debian-mips@lists.debian.org
ppc64el: debian-powerpc@lists.debian.org
riscv64: debian-riscv@lists.debian.org
s390x: debian-s390@lists.debian.org
There are some exceptions to these rules:
kfreebsd-i386: debian-bsd@lists.debian.org
kfreebsd-amd64: debian-bsd@lists.debian.org
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: debian-amd64@lists.debian.org instead.