Bug 9944 - patchtest-oe: check that patch was sent to the correct mailing list
Summary: patchtest-oe: check that patch was sent to the correct mailing list
Status: RESOLVED DUPLICATE of bug 10688
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchtest (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 2.3 M3
Assignee: Leonardo Sandoval Gonzalez
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-07-14 20:59 UTC by Leonardo Sandoval Gonzalez
Modified: 2017-12-06 17:03 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Leonardo Sandoval Gonzalez 2016-07-14 20:59:29 UTC 
It is pretty common to see patches on the wrong list (bitbake patches sent to oe-core ML or meta related patches sent to bitbake ML). This check can be done on the patchtest test suite.
Comment 1 Leonardo Sandoval Gonzalez 2016-10-27 21:40:33 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).
Comment 2 Leonardo Sandoval Gonzalez 2016-10-31 16:55:12 UTC 
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
Comment 3 Leonardo Sandoval Gonzalez 2017-01-25 17:51:18 UTC 
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.
Comment 4 Leonardo Sandoval Gonzalez 2017-02-08 20:44:58 UTC 
bug 10688 covers this case and also provides to the user the correct list (if found) so making this one as duplicated.

*** This bug has been marked as a duplicate of bug 10688 ***