Am 09/22/2016 11:41 PM, schrieb Matthias Seidel:
Am 22.09.2016 um 23:30 schrieb Marcus:
thats great news. Thanks for testing these issues. Of course we can
see if the fixes can be merged into 4.1.4, too. But to know by now
that it's no longer occurring with 4.2.0 is really valuable.

Therefore please can you write a note into the issues that you have
tested with a 4.2.0 dev build of SVN r1761670 and that the problem is
no longer visible?



great, I've changed some fields to reflect the fix in 4.2.0.

What about this issue? Is this also fixed?

If I look at there seems
to be only one line of code changed?

Even better when this is the entire fix. Looks not too risky for a merge.


Am 19.09.2016 um 19:30 schrieb Andrea Pescetti:
Matthias Seidel wrote:
[ ]
But the fix should be included in one of the next releases.
As well as:

Both should be nominated for 4.1.4. If you can check, on a trunk build
from a buildbot, that they are fixed on trunk ("4.2.0-dev"), this
would be a useful information. If you don't know where to find
buildbot builds, just ask.


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to