On 28/10/2019 23:01, Carlos Rafael Giani wrote:
Hm, true. Alright, I'll do that. For discussions about the recipe changes, should I create a fork of oe-core and place them there, just like how one would prepare merge requests? To me, it sounds more efficient than posting the patches in the mailing list for discussing them.
You can create a fork to ease merging, but review happens by patches sent to this list.
And speaking of upgrades, my changes are against 1.16.1, so the 1.16.0 -> 1.16.1 upgrade needs to make it into master-next in first.
Queued in ross/mut already. Ross -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
