10756 2016-12-01 20:46:21 +0000 patchwork: New patch revision messages should be processed even if they have a duplicated message-id 2017-12-06 17:19:10 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchwork 2.3 x86 Multiple RESOLVED FIXED Medium+ normal 2.3 M3 1 jose.a.lamego jose.a.lamego bluelightning brian.avery leonardo.sandoval.gonzalez patrick.ohly --- --- No (bug/feature does not impact docs) oldest_to_newest 68795 0 jose.a.lamego 2016-12-01 20:46:21 +0000 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/ 70565 1 jose.a.lamego 2017-02-08 22:19:44 +0000 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 70639 2 jose.a.lamego 2017-02-10 22:19:51 +0000 This is implemented in: http://git.yoctoproject.org/cgit/cgit.cgi/patchwork/commit/patchwork/bin/parsemail.py?id=267bf8752ea8665c5e503eb80ca01e618f9fd4c0