On Mon, 2022-07-04 at 16:24 +0200, Alexander Kanavin wrote: > On Mon, 4 Jul 2022 at 15:55, Richard Purdie > <richard.pur...@linuxfoundation.org> wrote: > > I guess the go one might, and using it as a template for some of our > > other workarounds might also help some of the other patches upstream > > but I have no connection to golang so help there from anyone with > > better connections might help. > > > > The gperf one is a workaround, I doubt it would be accepted upstream > > unfortunately but I'm also not sure what else we can do about the > > issue. > > Right, I was just asking to go through the mechanics of the upstream > submission. Basically trying to keep that weekly pending number from > going up :) Maybe just the gperf patch then? If they don't want the > patch, that's fine.
FWIW I've tried to join the bug-gperf list and sent the patch there but it is very inactive and I think things are stuck waiting for a moderator for the join and email. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#167623): https://lists.openembedded.org/g/openembedded-core/message/167623 Mute This Topic: https://lists.openembedded.org/mt/92128673/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
