The layer index does already support this, it's just not exposed (at the time I introduced it - some time ago - I thought it might encourage people to deviate from the release branch names, but in

Hi folks I've been looking into a couple of compiler flags for hardening that I think we might want to consider enabling by default in security-flags.inc: 1) -fstack-clash-protection This option

Once a week has proven a bit too hectic: it's better to have more time to test, submit, review and integrate the updates before AUH runs again. Signed-off-by: Alexander Kanavin

Jon, I've looked over all the changes and agree with Ross on his one suggestion and that the rest of the changes are fine. The new terms are equally or in some cases more clear so hopefully that

All, Our next OpenEmbedded Happy Hour is on January 26 for Europe/Americas timezones @ 1700/5pm UTC (12pm ET / 9am

The idea is we're trying to use the language which makes sense and "devel" says what the branch is/does. Cheers, Richard

A wrong path was given given the working directory. Also revert the changes with "git reset --hard" to have a clean state before further branch switches. Signed-off-by: Michael Opdenacker

This is the only one that sticks out to me. I think it needs another _, SKIP_RECIPE and IGNORE_CVE. Other than that, +1. Will we have a bit of logic to detect the obsolete names being set and emit

Personally, the only advantage of 'main' is muscle memory of m[tab]. Semantically it's not the 'main' branch, it's the active development branch. Thus, devel. Ross

Current Dev Position: YP 3.5 M3 Next Deadline: 21th Feb. 2022 YP 3.5 M3 build Next Team Meetings: Bug Triage meeting Thursday Jan. 27th 7:30 am PDT

On Mon, Jan 24, 2022 at 8:18 AM Jon Mason <jdmason@...> wrote: %< SNIP %< Branch Names The “master” branches on the relevant OpenEmbedded and Yocto Project git trees will be changed to an

A build flagged for QA (yocto-3.5_M2.rc6) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.5_M2.rc6 Build hash information: bitbake:

This is an excellent proposal, the new variable names for bitbake & oe-core are clear and easy to understand. The layer index may need some modification to handle different layers having different

All, YP M+ or high bugs which moved to a new milestone in WW04 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 14697 Hang due to missing asyncio loop

All, The below were the owners of enhancements or bugs closed during the last week! Who Count alex.kanavin@... 8 tim.orling@... 1 randy.macleod@... 1 JPEWhacker@... 1 Grand

All, Below is the list as of top 43 bug owners as of the end of WW04 of who have open medium or higher bugs and enhancements against YP 3.5. There are 67 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

I am looking for Custom SDK with filtered Header files/libraries based on some rules/approvals. It means not all files from YoctoSDK will be packaged in the CustomSDK. What is the mechanism or

From the beginning, OpenEmbedded and The Yocto Project have always strived to be as inclusive as possible to all races, sexes, orientations, religions, nationalities, and any other thing which might

From: Stefan Schmidt <stefan.schmidt@...> Instead of looking in PATH on the host to find bossac we now depend on the native variant we build and set the path to our yocto build