On 2017-07-10, Florian Viehweger <open...@out-of-creativity.de> wrote: >> I don't think it's really documented anywhere prominent, an errata >> would be the usual place for something like this but they aren't >> usually done without a code patch that can be applied.. > > I've also stumbled across it. If an errata is not in real prospect, > maybe a little notice in the upcoming 6.2 documentation?
It won't affect 6.2 as the problem was fixed after 6.1 release was tagged.
