summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorQuentin Schulz <quentin.schulz@cherry.de>2025-02-05 14:58:40 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-02-06 10:40:10 +0000
commit64ef07f6c4ad1e9d836236f71032b77f7c6b5248 (patch)
treec7dace18b6793f78469c09b0313dc35b8368bf8d /scripts
parent069a3460360e5b0fda433f30d96ce18db5a7d75c (diff)
downloadpoky-64ef07f6c4ad1e9d836236f71032b77f7c6b5248.tar.gz
bitbake: b4-config: Add basic support for b4 contribution workflow
b4[1] is a very nice tool for mail-based contribution. A config[2] file exists to set up a few defaults. We can use it to set the To recipients to always add, in our case the mailing list. This also adds a wrapper script that is called by b4 to figure out which addresses to put as Cc recipients. Considering that patches to the doc/ directory also need to be sent to the yocto-docs mailing list, this wrapper handles that. A limitation of the script (lsdiff actually) is that it doesn't know how to handle empty files, but those should be of rather rare occurrences. Because we currently do not have anything to check for patch validity, remove requirement for b4 prep --check to be run before sending a patch series, via disable-needs-checking in prep-pre-flight-checks. [1] https://pypi.org/project/b4/ [2] https://b4.docs.kernel.org/en/latest/config.html (Bitbake rev: 8843860010c97cc10ff69205d209634639b6c5cd) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions