Um, for 42.2 we share the same code base with SLE12-SP2, and we do not want to release this intrusive (backward incompatible) fix in SP2. We could create a separate branch for 42.2 and handle it specifically, but that causes some additional overhead. So we could do it if it is really important and worth the extra effort. Is that the case?