10739 2016-11-28 20:02:12 +0000 patchwork: pw should not create new revisions from comments/replies containing patch-like content 2017-12-06 17:18:54 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchwork unspecified x86 Multiple RESOLVED FIXED Medium normal 2.3 M3 1 jose.a.lamego jose.a.lamego bluelightning leonardo.sandoval.gonzalez patrick.ohly --- --- No (bug/feature does not impact docs) oldest_to_newest 68647 0 jose.a.lamego 2016-11-28 20:02:12 +0000 Pathchwork should identify message-replies that contain patch-like content and not create new series revisions from them. An example of such is revision 2 at: https://patchwork.openembedded.org/series/3843/ 68650 1 bluelightning 2016-11-28 20:33:12 +0000 How will you tell the difference between a genuine patch sent in reply to an earlier version (or even in reply to a discussion) and a reply with erroneous patch content? 68651 2 jose.a.lamego 2016-11-28 20:39:46 +0000 (In reply to comment #1) > How will you tell the difference between a genuine patch sent in reply to an > earlier version (or even in reply to a discussion) and a reply with > erroneous patch content? Exactly what I was wondering before filing this bug. I guess only after some investigation/testing I'll be able to answer. 68931 3 jose.a.lamego 2016-12-08 14:46:35 +0000 Another example: https://patchwork.openembedded.org/series/4235/ 69493 4 jose.a.lamego 2017-01-04 19:42:05 +0000 An example of a revision created from a reply (a ping, in this case) is at: https://patchwork.openembedded.org/series/4578/ and a revision created from reply: https://patchwork.openembedded.org/series/4506/#rev2 70625 5 jose.a.lamego 2017-02-10 17:32:15 +0000 "[PATCH" prefix is now mandatory for any email message to be considered as a possible new patch, and any message starting with any character other than square bracket will be considered only as a possible comment (for example, messages starting with "Re:" or "Fwd:"). This guideline will avoid the reported issue. This change is implemented in: http://git.yoctoproject.org/cgit/cgit.cgi/patchwork/commit/?id=1a096ecdec71ad20e47af075e0126f77c54e7ec9