Last entry is from December 2016 and there were many changes merged since then: http://lists.openembedded.org/pipermail/openembedded-commits/ It might be related to OE infrastructure changes or the updates of git hooks for patchwork (that's why it was reported for patchwork project - I haven't found "git" in Infrastructure bugs).
(In reply to comment #0) > Last entry is from December 2016 and there were many changes merged since > then: > http://lists.openembedded.org/pipermail/openembedded-commits/ > > It might be related to OE infrastructure changes or the updates of git hooks > for patchwork (that's why it was reported for patchwork project - I haven't > found "git" in Infrastructure bugs). Right. Although there are not many bugs on this area, bugzilla should have a product for the git.yp.org page.
This hook is simple enough to fix. Do we need to post the missed patches to the list or not? It seems like it would be spammy to send them at this point.
> Right. Although there are not many bugs on this area, bugzilla should have a product for the git.yp.org page. As long as it covers git.openembedded.org as well .. :) > This hook is simple enough to fix. Do we need to post the missed patches to the list or not? It seems like it would be spammy to send them at this point. If it's easy for you to post them then I think it would be better (it's always spammy in this list and most people probably filter it efficiently). For master-next I don't care at all (you probably cannot even re-create the e-mails, because the branches were rebased few times, so latest state doesn't cover the missed e-mails anyway - unless they are stuck in some postfix queue you're going to unblock now).
And the same issue exists in openembedded-core, meta-openembedded and probably also bitbake (if we had that hook there as well - I think we should).
This is working properly again. Thanks to Martin, Leo, and Jose for their troubleshooting help.