On Mon, Dec 13, 2021 at 05:30:05PM -0500, Trevor Woerner wrote:
Hi Quentin/Khem,No frustration on my side, just a debate/discussion on what we should
Would this have been solved by (me) creating a honister branch? I usuallyNo, the problem is the same because it is broken only in Honister 3.4.
So if we take this patch in, we basically have some code only for
"patching" honister 3.4 but anything different than that, the patch is
not necessary. So with a honister branch the "problem" stays the same.
The question is more what's the policy with that kind of patch. Would
you be ok taking that kind of patch which applies only to one dot
release of Yocto and nothing else? Or do we just ignore it until the
next dot release so it's fixed? Also do we expect to support honister
3.4 or once 3.4.1 is out (it is), we decide 3.4 is not supported at all?
I'd like at least to mention somewhere that meta-rockchip is supposed to
be used with something different than honister 3.4.
Anyway, it's ok not to answer now and hope a similar issue does not
happen later, or this discussion will be brought up again :)