Hi Mathieu,

Mathieu Othacehe <m.othac...@gmail.com> skribis:

>> So I think the right course of action would be to (1) delete it, (2)
>> recreate it starting from ‘core-updates’, and (3) reinstating the
>> relevant commits.
>
> Didn't know about that. Feel free to proceed to steps 1 and 2, and I'll
> take care of reinstating my cross-compilation related commits.

I’ve just deleted ‘core-updates-next’, and then recreated it on top of
‘core-updates’, with one extra commit by Mark:

567cca260d (origin/core-updates-next, core-updates-next) gnu: bash: 
Unconditionally configure PGRP_PIPE for *-linux systems.
e5efdbce21 (origin/core-updates, core-updates) gnu: perl-catalyst-view-json: 
Update to 0.37.
624ed47d41 gnu: perl-catalyst-runtime: Update to 5.90124.
27130ee8f7 gnu: libsmpeg: Fix build failure with GCC 7.
1f78a99964 gnu: perf: Really build without '-Werror'.

Could you push your commits there again?

Apologies for the inconvenience!

Thanks,
Ludo’.

Reply via email to