From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen.kooi@linaro.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libpng 1.6.13: fix build for aarch64
Date: Mon, 03 Nov 2014 16:08:32 +0000 [thread overview]
Message-ID: <1415030912.5111.31.camel@ted> (raw)
In-Reply-To: <9D7813D1-1BDC-4B46-BE6D-CF05049314E5@linaro.org>
On Mon, 2014-11-03 at 16:24 +0100, Koen Kooi wrote:
> Op 3 nov. 2014, om 13:10 heeft Richard Purdie <richard.purdie@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.burton@intel.com> het volgende geschreven:
> >>>
> >>>
> >>> On 3 November 2014 11:27, Koen Kooi <koen@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
next prev parent reply other threads:[~2014-11-03 16:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 12:12 [PATCH] libpng 1.6.13: fix build for aarch64 Koen Kooi
2014-11-03 9:57 ` Koen Kooi
2014-11-03 10:25 ` Burton, Ross
2014-11-03 11:27 ` Koen Kooi
2014-11-03 11:30 ` Burton, Ross
2014-11-03 12:06 ` Koen Kooi
2014-11-03 12:10 ` Richard Purdie
2014-11-03 15:24 ` Koen Kooi
2014-11-03 16:08 ` Burton, Ross
2014-11-03 17:13 ` Koen Kooi
2014-11-03 17:33 ` Burton, Ross
2014-11-03 16:08 ` Richard Purdie [this message]
2014-11-03 17:38 ` Mark Hatle
2014-11-03 17:44 ` Burton, Ross
2014-11-04 2:30 ` Kang Kai
2014-12-12 8:42 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1415030912.5111.31.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen.kooi@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.