Bug 10756

Summary: patchwork: New patch revision messages should be processed even if they have a duplicated message-id
Product: [Yocto Project Subprojects] Patchwork/Patchtest Reporter: Jose Lamego <jose.a.lamego>
Component: PatchworkAssignee: Jose Lamego <jose.a.lamego>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: bluelightning, brian.avery, leonardo.sandoval.gonzalez, patrick.ohly
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 Jose Lamego 2016-12-01 20:46:21 UTC 
New valid patch revisions may be received with email messages displaying a message-id header that duplicates that of the original revision. This messages are currently not processed by patchwork.
For example, message [1] didn't made into patchwork series: [2]

Although this may be produced by non-standard patch submission practices, it results in a poor user experience due to the fact that the revision does not made it into patchwork, so it is worth to investigate feasibility for an additional test for modified subject/content in these type of messages to identify valid revisions.

[1] http://lists.openembedded.org/pipermail/bitbake-devel/2016-December/008271.html

[2] https://patchwork.openembedded.org/series/4136/
Comment 1 Jose Lamego 2017-02-08 22:19:44 UTC 
A fix was implemented in patchwork-staging for testing and patch can be seen in:
https://lists.yoctoproject.org/pipermail/yocto/2017-February/034423.html