Hi, On 02/08/2011 05:15 PM, John Langley wrote:
I believe I'm seeing this in 2.1.3 as well. What's the likelihood of the fix being ported to the 2.1 branch?
Much higher now that someone asked for it. :-) I'll see to it that the fix gets included in the next 2.1.x release. -- Jukka Zitting
