Fast-forward to master?
I would like to suggest fast-forwarding the pyro branch of meta-gplv2 to master. The only change that I see as questionable is the change to mc, but since the change was accepted for master, I see no reason why it should not be acceptable for pyro (even though it is not necessary there).
//Peter
Quoted 5 lines · Peter Kjellerstedt
I would like to suggest fast-forwarding the pyro branch of meta-gplv2 to master. The only change that I see as questionable is the change to mc, but since the change was accepted for master, I see no reason why it should not be acceptable for pyro (even though it is not necessary there).
Agreed.
I'm planning to submit the gmp fix for aarch64 as a backport to the GPLv2 gmp recipe in oe-core morty, so the same fix needs to be available in pyro too. Fast-forwarding meta-gplv2 pyro currently looks safe and in this case maybe better than trying to submit just that one fix into the meta-gplv2 pyro branch.
Quoted 7 lines
//Peter
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 8 lines · Andre McCurdy
Quoted 5 lines · Peter Kjellerstedt
I would like to suggest fast-forwarding the pyro branch of meta-gplv2 to master. The only change that I see as questionable is the change to mc, but since the change was accepted for master, I see no reason why it should not be acceptable for pyro (even though it is not necessary there).
Quoted 7 lines
Agreed.
I'm planning to submit the gmp fix for aarch64 as a backport to the GPLv2 gmp recipe in oe-core morty, so the same fix needs to be available in pyro too. Fast-forwarding meta-gplv2 pyro currently looks safe and in this case maybe better than trying to submit just that one fix into the meta-gplv2 pyro branch.
Agreed, done.
Ross