| Summary: | We need a patchwork instance pointing to the Yocto mailing list | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | brian avery <brian.avery> |
| Component: | Patchwork | Assignee: | Michael Halstead <mhalstead> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | bluelightning, joe, juro.bystricky, mark.hatle |
| Version: | 2.3 | ||
| Target Milestone: | 2.7 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
brian avery
2017-02-06 21:06:50 UTC
+juro If we can use the patchwork instance on openembedded.org for this I think that would be fine - we don't really need one on yoctoproject.org as well IMO, we'd just create a separate project for it. I'm not sure if there are any logistical issues that would prevent that from working though. Following on a discussion we were just having on IRC, this would be really nice to have for meta-selinux maintenance and presumably it would benefit other projects without their own mailing lists as well. https://patchwork.openembedded.org/project/yocto/ is created and can start receiving patches. Please monitor closely for expected behavior these next several days. This has collected all patch series so far in December. I think this is working as expected. |