I am looking at 4.4 git repository and version -93 contains exactly the problem described here, it contains the commit# 46a704f8409f79fd66567ad3f8a7304830a84293 (as a97e978574f41ffcf1813c180aba2772d46fbb5b), but it does not include commit# e47057151422a67ce08747176fa21cb3b526a2c9.
That said, we probably want to include e47057151422a67ce08747176fa21cb3b526a2c9 into 4.4 series as soon as possible.
Christian,
I am looking at 4.4 git repository and version -93 contains exactly the problem described here, it contains the commit# 46a704f8409f79f d66567ad3f8a730 4830a84293 (as a97e978574f41ff cf1813c180aba27 72d46fbb5b) , but it does not include commit# e47057151422a67 ce08747176fa21c b3b526a2c9.
That said, we probably want to include e47057151422a67 ce08747176fa21c b3b526a2c9 into 4.4 series as soon as possible.