https://bugs.winehq.org/show_bug.cgi?id=41107
--- Comment #12 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Wylda from comment #11)
Thanks, this exactly what i wished ;) But could you help me bit more, please?
Of course, but our discussions are not really related to the bug itself. If you need more help with bisecting, it might be better if you ask for help in the #wine-staging IRC channel or if you contact me privately.
... to find the guilty patch using bisect without going back in history. Just check out wine git
Do you mean:
wine-git$ git checkout -f wine-1.9.16 staging-git$ git checkout -f v1.9.16
wine-git$ /path/to/wine-staging/patches/patchinstall.sh --backend=git --force-autoconf --all
Yes.
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.
Above git bisect commands should be in "wine-git" dir or "staging-git" dir?
In the wine-git dir.
Why plain "origin" (git bisect good origin) instead of version?
If you check out a versioned release it is indeed better to specify the same version number here. I was initially thinking about bisecting with the patches applied on top of the latest upstream commit, but it should also work like you suggested.