> Am 28.05.2019 um 14:36 schrieb Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>: > > Hey. > > Just to be on the safe side... > > AFAIU this issue only occured in 5.1.2 and later, right? No. The issue was already introduced in v5.1-rc1 (commit 61697a6abd24). > Starting with which 5.1.x and 5.2.x versions has the fix been merged? It's fixed in v5.2-rc2 (commit 51b86f9a8d1c) and v5.1.5 (commit 871e122d55e8). Cheers, Michael
