Bug 10756 - patchwork: New patch revision messages should be processed even if they have a duplicated message-id
Summary: patchwork: New patch revision messages should be processed even if they have ...
Status: RESOLVED FIXED
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchwork (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.3 M3
Assignee: Jose Lamego
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-12-01 20:46 UTC by Jose Lamego
Modified: 2017-12-06 17:19 UTC (History)
4 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 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