http://bugs.winehq.org/show_bug.cgi?id=5535
--- Comment #56 from Friedrich Göpel shado23@gmail.com 2008-06-11 11:44:13 --- (In reply to comment #55)
Friedrich Göpel, if you can fix this bug or know someone who can then go ahead, submit patches for it, but Wine is worked on by -volunteers- not people paid to fix it, they generally work on the parts where their skills are best utilised and what they actually have time to accomplish. There just isn't anyone here to fix this bug at the moment (or in the past) else it likely would have already been fixed.
I do realize that this is a volunteer run project, where you can't force anyone to do anything. That wasn't really my intention anyway.
My point was just this specific bug being a regression, which I assumed would be treated differently for 1.0 than some random bug. For example if this were the linux kernel, the person doing the fancy new rewrite would be expected to fix the resulting regressions, or it would get reverted if that was not possible and the regression wasn't just a nuisance. Of course this can't be done 2 years later.
I can't fix the bug either, but I assume that the author of the commit that introduced this has probably the most insight in what might be to blame and what not than some random person not familiar with wine internals.
In any case I'll shut up now, and apologize if I sounded demanding or insulting at any point.