| Summary: | patchtest-oe: check that patch was sent to the correct mailing list | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez> |
| Component: | Patchtest | Assignee: | Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | bluelightning, sgw |
| Version: | 2.3 | ||
| Target Milestone: | 2.3 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Leonardo Sandoval Gonzalez
2016-07-14 20:59:29 UTC
Currently, patchtest is only monitoring oe-core, which means that patch basenames must start with 'meta' or 'scripts'. However, for the latter, some patches can either go to oe-core or poky. Before implementing the bug, we need to have this mapping clear (scripts files --> project). One extra check: if shortlog has a sub string including a targeted non-meta layer, this would intermediately indicate that it was sent to the wrong list. For example: http://lists.openembedded.org/pipermail/openembedded-core/2016-October/128186.html This check is important because quite often contributors send patches to the wrong list. Raising the importance (from M to M+) and should be ready by M3. |