https://bugs.winehq.org/show_bug.cgi?id=41107
--- Comment #10 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Wylda from comment #9)
I was wondering, that someone could put here educated guess about a patches to save me some time.
But latter today, i could make manual bisection per re-base commits based on staging's commit history between 1.7.52 and 1.7.53 to pinpoint exact patch set. Or is there a better way in case of staging?
My best guess would be:
https://github.com/wine-compholio/wine-staging/tree/master/patches/server-Si...
However, there is also an easy way to find the guilty patch using bisect without going back in history. Just check out wine git, then use:
/path/to/wine-staging/patches/patchinstall.sh --backend=git --force-autoconf --all
This will add all patches as separate commits with their corresponding autogenerated changes. Then just do:
git bisect start git bisect good origin git bisect bad
And then continue bisecting as usual. You might have to re-run ./configure if compilation aborts because of Makefile changes.