Contribute/MailingLists: Difference between revisions
No edit summary |
|||
| Line 13: | Line 13: | ||
* [https://lists.nongnu.org/mailman/listinfo/qemu-riscv QEMU RISC-V mailing list] | * [https://lists.nongnu.org/mailman/listinfo/qemu-riscv QEMU RISC-V mailing list] | ||
* [https://lists.nongnu.org/mailman/listinfo/qemu-s390x QEMU s390x mailing list] | * [https://lists.nongnu.org/mailman/listinfo/qemu-s390x QEMU s390x mailing list] | ||
If a subsystem maintainer thinks that a new mailing list for their subsystem would make life easier, we're happy to create one -- mail qemu-devel to suggest it (ideally cc'ing the people listed as Savannah project admins in our [[AdminContacts]] page, as they are the ones with the ability to make the change). | |||
If you are a Savannah project admin, you may want the [[Contribute/MailingLists/Creation|technical notes on how to create and configure a new list]]. | |||
Revision as of 14:56, 30 October 2018
- QEMU developers mailing list
- QEMU stable mailing list
- QEMU trivial patch mailing list
- QEMU users mailing list
Subsystem Specific Lists
These exist to make it a little easier to follow subsystem specific patches. You should however continue to CC qemu-devel so your series gets wide visibility.
- QEMU ARM mailing list
- QEMU block devices mailing list
- QEMU PowerPC mailing list
- QEMU RISC-V mailing list
- QEMU s390x mailing list
If a subsystem maintainer thinks that a new mailing list for their subsystem would make life easier, we're happy to create one -- mail qemu-devel to suggest it (ideally cc'ing the people listed as Savannah project admins in our AdminContacts page, as they are the ones with the ability to make the change).
If you are a Savannah project admin, you may want the technical notes on how to create and configure a new list.