diff options
| author | Quentin Schulz <quentin.schulz@cherry.de> | 2025-02-07 12:46:35 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-02-10 13:03:58 +0000 |
| commit | 31a537d12441e4bcaf3f15e7807a5092ee61d7f1 (patch) | |
| tree | 5fe13b6d98101e415fc925394b3b8cf66c5612ab /meta/recipes-devtools/python/python3/0001-Lib-sysconfig.py-use-prefix-value-from-build-configu.patch | |
| parent | a886f0a8cdb4fd98f68b7494c666878fadf4626f (diff) | |
| download | poky-31a537d12441e4bcaf3f15e7807a5092ee61d7f1.tar.gz | |
b4-wrapper-poky.py: send changes to .b4-config to the poky mailing list
Both OE-Core and poky git repos have a .b4-config, both at the same
location and both different.
Therefore, changes made to .b4-config for OE-Core need to be sent to the
OE-Core mailing list and changes made to .b4-config for poky sent to the
poky mailing list.
Changes made to OE-Core's .b4-config can only be made from a vanilla
OE-Core git repo, not from poky git repo. With the current content of
OE-Core's .b4-config, b4-wrapper-poky.py script is NOT called to figure
out where to send patches, b4 gets it from the hardcoded value in
send-series-to.
Thus, we can say that if b4-wrapper-poky.py detects changes for
.b4-config, those changes are for poky since this script wouldn't be run
by b4 outside of poky git repo.
(From OE-Core rev: 1006712027812326fdeade2ab539b42bdf5b10e6)
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/python/python3/0001-Lib-sysconfig.py-use-prefix-value-from-build-configu.patch')
0 files changed, 0 insertions, 0 deletions