@Chris: no, it will be fixed in 3.5.2, pitti said it's ok to wait until the next version since the fix is already in upstream git and we can't miss it
@Chris: no, it will be fixed in 3.5.2, pitti said it's ok to wait until the next version since the fix is already in upstream git and we can't miss it