https://bugs.kde.org/show_bug.cgi?id=368507
--- Comment #5 from Julian Seward <jsew...@acm.org> --- I had hoped to do this for 3.12.0, but after looking at the #ifdef swamp in VG_(am_startup) that sets aspacem_maxAddr, I think it is too risky, because of the number of different cases that need to be verified. So I'd propose to leave it till after the release. The number of users that this will affect is tiny and those that really need it in 3.12.x can cherry pick the trunk commit into their own custom 3.12.x build, once we fix it on the trunk. -- You are receiving this mail because: You are watching all bug changes.
