http://bugs.winehq.org/show_bug.cgi?id=16135
--- Comment #11 from Tim Holy holy@wustl.edu 2011-03-30 04:59:47 CDT --- (In reply to comment #10)
Still unimplemented, please resend.
Are you a wine developer? If so, can you tell me what resending means? Option 1: I can mail my old patch as-is to wine-patches. This is very easy, and I am happy to do it. But, it probably won't apply cleanly to the source tree now, because it is more than two years old. Option 2: I can download the wine source tree (I don't have it any more), try to figure where my patch applies, update my patch, and re-send it to the list.
Option 2 is not hard, but would take me a nontrivial amount of time (I don't use git, etc.). I'm willing to put some effort in for the sake of the community, but there seems little reason to do it without some evidence that it is more likely to get applied this time. This particular issue no longer affects me, so my own intrinsic motivation is fairly low, especially since it was never accepted in the first place despite some very helpful review by Juan Lang (a wine developer).
If you are a wine developer and simply asking me to clean up my work before you ensure it gets in, I am happy to do that: it is a small exchange for the many benefits I receive from running wine! If you're not a wine developer, but this issue affects you, then the problem is that I could do #2 and it still might not get in. In that case, I think you may be better suited to push for this yourself, because you can give examples that fail without it (I can't do that anymore, because I don't run that old program anymore, so I can't even test this patch, though it did work in 2008), and you care about the outcome. You could certainly download the patch and do #2 on your own.