On Thu, Oct 5, 2023 at 10:13 AM Martin Jansa wrote:
> FWIW: I prefer oe-core keeping master and nanbield in sync (even using the
> same SHAs) until they really need to be different
>
> Now there is the Maintainer change in READMEs already applied in nanbield,
> so the commits from master won't be
FWIW: I prefer oe-core keeping master and nanbield in sync (even using the
same SHAs) until they really need to be different
Now there is the Maintainer change in READMEs already applied in nanbield,
so the commits from master won't be idential SHAs. Next time it would be
IMHO better to delay merg
Hi Peter,
We have created the branch since there were some patches moving
python3 recipes to core which were not sure if they will make into
this release
or not. Plan was to keep it in sync with master as far as possible.
Good part is that those python recipe move has made into core in
nanbield so
On 10/5/23 7:01 AM, Peter Kjellerstedt wrote:
Khem and Armin,
what are the plans for the nanbield branch, given that is was
branched off long before the actual Nanbield release? Do you plan
on merging master into it once Nanbield is released, or will it
stay as it is and relevant parts will ha
Khem and Armin,
what are the plans for the nanbield branch, given that is was
branched off long before the actual Nanbield release? Do you plan
on merging master into it once Nanbield is released, or will it
stay as it is and relevant parts will have to be backported?
The reason I ask is beca
