On Sat, 16 Sep 2017 02:22:01 +
Will Page wrote:
> Thanks, Ross.
>
> I had contacted the maintainer off list to ask where I should submit
> my patch. I may have misunderstood his reply.
No, I'm just confused, because I'm not really otherwise active in
yocto/oe-core these days, I just still
On Sat, Sep 16, 2017 at 7:41 AM, Martin Jansa wrote:
> Just the commit IDs from the top won't be very useful, because it's from
> jansa/master branches which are rebased even more often than master-next.
>
> If you really want to see them, then there are links to the build logs for
> each MACHINE
Just the commit IDs from the top won't be very useful, because it's from
jansa/master branches which are rebased even more often than master-next.
If you really want to see them, then there are links to the build logs for
each MACHINE and you can see the build configuration there.
That's why at t
On Sat, Sep 16, 2017 at 2:00 AM, Martin Jansa wrote:
> Probably is, qemux86 was built from slightly older metadata, so probably
> including previous versions of your klibc changes.
>
> I know it's confusing in the report, but still each build takes around 24
> hours per machine and I have only 2 b
Probably is, qemux86 was built from slightly older metadata, so probably
including previous versions of your klibc changes.
I know it's confusing in the report, but still each build takes around 24
hours per machine and I have only 2 builders. e.g. this qemux86 build was
started 20170912_234104