http://bugs.winehq.org/show_bug.cgi?id=31237
--- Comment #4 from Alexandre Julliard julliard@winehq.org 2012-07-19 05:15:09 CDT --- (In reply to comment #3)
(In reply to comment #1)
To do it right you'd need to ensure that all processes running under the same wineserver see the same time, so even tracking child processes wouldn't be sufficient. It would need a convincing use case to be worth the effort.
So that sounds like you would be open to patches, anyway. Is that right?
Is there any guidance on what might make a "convincing use case"? There are a lot of use cases, but they do tend to be pretty niche. Another example is for testing a program e.g. to see if it handles expired certificates correctly, or if it works correctly on a leap day.
That sort of niche use case can be handled by maintaining a separate patch that you apply for testing. I wouldn't consider it important enough to justify adding the feature to the main code base.