Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=master 2025-11-07T16:36:50+00:00 2025-11-07T16:36:50+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2025-11-07T16:36:30+00:00 urn:sha1:453df63af0c857c24804271da7f55691d0ed27f8 You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs https://docs.yoctoproject.org/dev/dev-manual/poky-manual-setup.html b) use the new bitbake-setup https://docs.yoctoproject.org/dev/dev-manual/poky-manual-setup.html You can find more information in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2025-02-06T10:40:55+00:00 Quentin Schulz quentin.schulz@cherry.de 2025-02-05T15:12:56+00:00 urn:sha1:65e773f88b78ece2b4f4e117a0ce9ee5e84e6464 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 provide the Cc and To recipient list for the series. This uses the b4-wrapper-poky.py script for checking that each patch in the series is only for one project. Indeed, poky is actually a "collection" of multiple repositories, namely BitBake, OpenEmbedded-Core and the Yocto Docs. One patch should therefore not make changes in multiple of those projects otherwise it cannot be merged. Additionally, a check is added to make sure that a series only touches files from one project to avoid having to figure out which patch is to be merged by which maintainer in which project repo. Moreover, it is not uncommon to have people develop patches for those projects from within poky. This wrapper figures out which mailing lists to send patches to based on the files that are modified in the series. Considering that patches to the bitbake/doc/ directory need to be sent to both the bitbake and yocto-docs mailing list (To recipient for the former, Cc recipient for the latter) 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. Note that this script requires hardcoding of paths that are handled by different projects to map files to projects. Anything not mapped is assumed part of OE-Core. [1] https://pypi.org/project/b4/ [2] https://b4.docs.kernel.org/en/latest/config.html Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>