https://bugs.winehq.org/show_bug.cgi?id=40613
--- Comment #31 from Erich E. Hoover erich.e.hoover@gmail.com --- (In reply to Louis Lenders from comment #28)
... i don`t know how to do a "wine-staging regression test", but atm word "Staged" is not valid...
1) Find the major version where things go from working to broken, since this saves a lot of time and effort narrowing in. 2) Once you have the major versions involved the easiest thing to do is to check out Wine for the working version and apply all of the staging patches to it and confirm that that still works (no issues from being compiled differently). 3) Export all the patches in mbox format so that they are easy to add and remove 4) Reset to the working major version and start a bisect between the working and broken versions 5) At each step along the bisect apply the mbox patches (rework them if necessary), test, and then unapply them (git bisect [good|bad] doesn't work on a modified tree) 6) Once you have found the "broken" Wine commit then try to determine if the problem is related to the Wine commit or an unintentional/rebase change in a Wine-Staging commit. Usually it's pretty obvious if it's a rebase problem because the "broken" commit touches some code that you had to rework to get the Wine-Staging patches to apply.