The OE TSC discussed improving our patch submission tools to include template messages about the kinds of things that could be included in the commit messages and pull request summary. A suggestion about what one company used is included below. This enhancement request is to investigate the possible solutions and propose something to be adopted.

This would be to encourage users to include more information in commit messages including what testing had been made of patches.


From $USER@${myname} ${yesterday}
From: $(my_email)
To: ${mailto}
Cc: ${mailcc}
Date: ${today}
Subject: Review request 0/$patch_count: INSERT 10 WORD SUMMARY HERE [ $(squash_cq $cqid) ]
 
Summary:
Tech Review:
Gatekeeper:
Lockdown Approval (if needed):
Branch Tag: $remotehead
IP Statement (form link or license statement):
Parent Template (where applicable):
 
-------------------------------
Impacted area       Impact y/n
------------------- -----------
docs/tech-pubs          n
tests                   n
build system            n
host dependencies       n
RPM/packaging           n
toolchain               n
kernel code             n
user code               n
configuration files     n
target configuration    n
Other                   n
 
Comments (indicate scope for each "y" above):
---------------------------------------------
$(all_git_log $range)
 
Added Files:
------------
$(files_changed added)
 
Removed Files:
--------------
$(files_changed removed)
 
Remaining Changes (diffstat):
-----------------------------
$(files_changed changed)
 
Testing Applicable to:
----------------------
 
Testing, Expected Results:
--------------------------
 
 
Conditions of submission:
-------------------------
 
 
Arch    built      boot     boardname
-------------------------------------
MIPS      n         n
MIPS64    n         n
MIPS64n32 n         n
ARM       n         n
x86       n         n
x86_64    n         n
PPC       n         n
PPC64     n         n