On Dec 30, 2021, at 17:41, Chris Jones wrote:
> Hi
>
> Before arm came along the gccdevel ports indeed did not update that regularly.
They did some years ago. Then for a time they didn't.
> Normally in the run up to a new major release they might see more activity,
> as we take a look as to if
Hi
Before arm came along the gccdevel ports indeed did not update that regularly.
Normally in the run up to a new major release they might see more activity, as
we take a look as to if the upcoming release has any issues, but outside that
they perhaps would go a month or two between updates. Ar
>> It seems like we’re updating this port at least weekly. With the result
>> being that our Intel buildbots are routinely bogged down for a long time,
>> sometimes as long as 4-5 hours.
>>
>> While I understand that we want to follow upstream’s progress - particularly
>> for the ARM version -
> It seems like we’re updating this port at least weekly. With the result being
> that our Intel buildbots are routinely bogged down for a long time, sometimes
> as long as 4-5 hours.
>
> While I understand that we want to follow upstream’s progress - particularly
> for the ARM version - is thi
It seems like we’re updating this port at least weekly. With the result being
that our Intel buildbots are routinely bogged down for a long time, sometimes
as long as 4-5 hours.
While I understand that we want to follow upstream’s progress - particularly
for the ARM version - is this really nec
