On Fri, Apr 22, 2016 at 9:34 AM, Ralf Corsepius <rc040203@freenet.de> wrote:

How about
* filing a BZ against Coin3 such that the Coin3 maintainer (me) gets informed and has a chance to reproduced the issue?

* filing and proposing a patch in advance, instead of rushing out patch?

Apologies, of course you are right. I just got so wrapped up into trying to figure out what the problem is.

The fix (if appropriate) should also probably be sent to the upstream issue tracker.

Thanks,

Richard