@Werner, my understanding was that this fix is in git already? Since the last change is from 2013 in that file it would be out already. About which change/fix do we speak exactly here?