summaryrefslogtreecommitdiff
path: root/meta-openembedded/meta-oe/recipes-support
diff options
context:
space:
mode:
authorEd Tanous <edtanous@google.com>2021-09-09 21:46:43 +0300
committerEd Tanous <ed@tanous.net>2021-09-18 00:59:42 +0300
commit7f8954e7a7576c28a6773be2f0e306551c0aa754 (patch)
tree3b0343b283b37d484e719512b4236f52b88b47ee /meta-openembedded/meta-oe/recipes-support
parentd5cea14bea968d361eea32efa51e26c43093504f (diff)
downloadopenbmc-7f8954e7a7576c28a6773be2f0e306551c0aa754.tar.xz
Implement a test for patch compliance
Per our documentation, patches outside of a couple specific directories aren't allowed. This commit implements a build-time check to see if any new patches have been added. Functionally, because there's several meta layers that have broken the rules already, it has to contain a check against the various patches that already exist in the tree. This list doesn't constitute a grandfather-ing in of those patches, but recognizes that we can't immediately back them out, and having the maintainers take care of them will take time. Of note, this patchset also ignores patches in any of the poky layers, as we can't define their policies, and allows patches in meta-phosphor, as a backdoor in case we need a trapdoor to this policy, and all the maintainers agree to it. This change was originally checked into openbmc-build-scripts, but was moved to support more users, and keeping this list up to date. All comments on the latest review from https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-build-scripts/+/46064/2 have been addressed. Change-Id: I1c3e062278b4856cbfda910bdbf122e4b7539f89 Signed-off-by: Ed Tanous <edtanous@google.com>
Diffstat (limited to 'meta-openembedded/meta-oe/recipes-support')
0 files changed, 0 insertions, 0 deletions