On 08/16/2009 10:14 AM, Jürgen Spitzmüller wrote:
rgheck wrote:
Maybe the thing to do is not include it for 1.6.4, but commit it as soon
as 1.6.4 is out, so that it gets tested. I doubt that terribly many
people get bit by this bug. Not to say it isn't important, but we don't
want to make things worse...
Actually, I tend to agree.
We could also just commit your patch which pops up a warning on buffer
destruction if a buffer is dirty.
My patch too is delicate. I think it's fine, but there may still be a
possibility of people being asked multiple times if they want to save a
document. I guess that's not so bad, but if you want me just to commit
that one, then we can do that. It at least solves the dataloss problem,
and then we can commit Vincent's patch for 1.6.5.
rh
