On Mon, 2014-11-03 at 16:24 +0100, Koen Kooi wrote: > Op 3 nov. 2014, om 13:10 heeft Richard Purdie > <richard.pur...@linuxfoundation.org> het volgende geschreven: > > > On Mon, 2014-11-03 at 13:06 +0100, Koen Kooi wrote: > >>> Op 3 nov. 2014, om 12:30 heeft Burton, Ross <ross.bur...@intel.com> het > >>> volgende geschreven: > >>> > >>> > >>> On 3 November 2014 11:27, Koen Kooi <k...@dominion.thruhere.net> wrote: > >>>> Last night I was looking at my "post-1.7" tag and the number of aarch64 > >>>> patches there. Kai, did you continue work on that staging branch for > >>>> all of the aarch64 patches that were being posted? > >>> > >>> What does that have to do with this patch? > >>> > >>> Kai was collecting patches that were sent to oe-core, and this may have > >>> been one of them. > >> > >> Is this some new requirement for OE-core patches? > > > > Its someone being helpful and trying to consolidate a topic branch and > > test things before it gets merged. > > > > So its not a new requirement but it is helpful and appreciated. > > It's been over a month and libpng is still broken, so I refuse to > classify this new process as 'helpful' or as 'appreciated' at this > point.
Well, for the past month we've been freezing for and working toward the release and it was agreed this batch of patches were being queued for post release. I think that was quite clear. As you well know, partly this is because we don't have a way to test any of it, nor is it an officially supported target. If we get a consistent set of code and a qemu machine that can test it, we'll be in a better position and I believe that is something people are working towards (but was way too late for the 1.7 cycle). We're now in a position where we've started merging patches again, there is a backlog being worked through and I'm sure this batch will be presented soon. We are sticking with the stated plan which was to have a queued branch of those patches, until such times as there is a better plan or offer. > If this continues can the person doing such a branch reply to patches > intended for it saying they will or won't be queued? And please run > the patches without such a reply through the regular process. That > would be both helpful and appreciated. It would be nice if the folks at Linaro would actually present things like a branch containing theire changes and help with this work. As it is, it seems others need to do this for them and instead they just want to complain why we don't take patches (which often don't even seem to build). I can understand not everyone at Linaro is going to test patches on a couple of other arches but having someone there aggregating patches and doing some acid tests might massively improve both their reputation and increase the chances of patches merging in a timely fashion. Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
