Bug 11518 - Upstream-Status Submitted and Inappropriate check for where/reason info
Summary: Upstream-Status Submitted and Inappropriate check for where/reason info
Status: RESOLVED FIXED
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchtest (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 2.5 M1
Assignee: Daniela Plascencia
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-05-17 14:38 UTC by Leonardo Sandoval Gonzalez
Modified: 2017-10-19 19:57 UTC (History)
1 user (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 2017-05-17 14:38:50 UTC 
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
Comment 1 Daniela Plascencia 2017-08-17 20:41:27 UTC 
Moving to M4 waiting for an execution issue to be solved (bitbake/tinfoil related).
Comment 2 Daniela Plascencia 2017-09-12 21:39:00 UTC 
Should this check be inside the format unit test or be set as a separate one?
Comment 3 Leonardo Sandoval Gonzalez 2017-09-12 21:43:20 UTC 
(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
Comment 4 Daniela Plascencia 2017-10-02 15:40:17 UTC 
Moving to 2.5 M1, I'll work on all enhancements on such milestone.