2016-03-31 18:52 GMT+01:00 Nikos Tsipinakis <ni...@tsipinakis.com>: > 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?
It would matter if the patch that you're going to apply was the old patch that was first added for 2.9 to fix a problem in 2.8, and then disappeared for unknown reasons before 2.9 was actually released. Maybe the reasons were actually that upstream specifically reverted the patch before 2.9 because of causing other problems. That was my reason for asking. Since the one that you want to apply was added after 2.9, I suppose that it's fine :) -- Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
