On Thu, Mar 31, 2016 at 05:46:32PM +0100, Manuel A. Fernandez Montecelo wrote:
> Uhm, sorry for not being clear. I know that the Debian maintainers
> were busy with other stuff.
>
> What it was not clear to me was why this was present in both 2.8 *and*
> 2.9 upstream, e.g., if the original patch had been reverted because it
> caused other problems.
Oh, I am not really sure. I havent followed the 2.9 development that closely and
I really dont feel like digging into 2 years worth of commits to find out, its
fixed anyway so does it really matter?
--
Best Regards,
Nikos Tsipinakis
