9873 2016-07-04 16:32:52 +0000 patchtest-oe: in case LIC_FILES_CHKSUM changed, make sure commit message indicates the reason 2017-12-06 16:56:49 +0000 1 1 6 Yocto Project Subprojects Patchwork/Patchtest Patchtest 2.1 x86 Multiple RESOLVED FIXED Medium+ enhancement 2.2 M2 1 leonardo.sandoval.gonzalez jose.a.lamego bluelightning richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 63632 0 leonardo.sandoval.gonzalez 2016-07-04 16:32:52 +0000 The suite must at least check that subject contains the string 'lic_files_chksum' or 'license' or 'checksum' in case the value of LIC_FILES_CHKSUM would change on behalf of the corresponding patch. 63662 1 bluelightning 2016-07-06 02:16:15 +0000 By "subject" you mean "commit message" here. 63668 2 leonardo.sandoval.gonzalez 2016-07-06 13:47:22 +0000 (In reply to comment #1) > By "subject" you mean "commit message" here. patchtest at the end is using mboxes (which contain code changes in the payload), so in patchtest context is indeed a subject. 63688 3 bluelightning 2016-07-06 20:05:42 +0000 The subject is the shortlog from the commit message, not the entire commit message. LIC_FILES_CHKSUM would typically be mentioned in the commit message but not the shortlog - hence in email terms it would not actually appear in the subject, just the message body. 63690 4 leonardo.sandoval.gonzalez 2016-07-06 20:30:30 +0000 (In reply to comment #3) > The subject is the shortlog from the commit message, not the entire commit > message. LIC_FILES_CHKSUM would typically be mentioned in the commit message > but not the shortlog - hence in email terms it would not actually appear in > the subject, just the message body. I see. I was a misunderstood from my part. Thanks for clarifying this.