11518 2017-05-17 14:38:50 +0000 Upstream-Status Submitted and Inappropriate check for where/reason info 2017-10-19 19:57:31 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchtest 2.4 x86 Multiple RESOLVED FIXED Medium+ enhancement 2.5 M1 1 leonardo.sandoval.gonzalez daniela.plascencia bluelightning --- --- No (bug/feature does not impact docs) oldest_to_newest 73296 0 leonardo.sandoval.gonzalez 2017-05-17 14:38:50 +0000 According to [1], the submitted and inappropriate upstream-states must provide info to either where the patch was submitted or why the patch is inappropriate. [1] http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations 75967 1 daniela.plascencia 2017-08-17 20:41:27 +0000 Moving to M4 waiting for an execution issue to be solved (bitbake/tinfoil related). 76768 2 daniela.plascencia 2017-09-12 21:39:00 +0000 Should this check be inside the format unit test or be set as a separate one? 76769 3 leonardo.sandoval.gonzalez 2017-09-12 21:43:20 +0000 (In reply to comment #2) > Should this check be inside the format unit test or be set as a separate one? inside. This should be part of test_patch_upstream_status.test_upstream_status_format 77270 4 daniela.plascencia 2017-10-02 15:40:17 +0000 Moving to 2.5 M1, I'll work on all enhancements on such milestone. 77715 5 daniela.plascencia 2017-10-19 19:57:31 +0000 Merged at http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe/commit/?id=4a1ae9cb768be7086712801b3c53a404b4cd5b83