> I don't know. I'm always only focused on the combination of user-visible
> changes and risks of bugs (which are user-visible changes btw). So if we
> can do it without breaking too much code, then it can be backported. What
> we have now is something which is apparently insufficient to some users
> so we can improve the situation. I wouldn't want to remove prefer-* or
> change the options behavior or whatever for example.
Ok, if we don't remove existing prefer-* keywords a 1.6 backport sounds
possible without user visible breakage, great.
lukas
