> If the bisect identifies a patch that a developer believes is harmless, you may be asked to check the result by reverting that patch. > First, reset the bisect if you haven't already: > > Code: > git bisect reset > > > Then use the revert command with the sha1 id of the bad patch: > > Code: > git show b821e839bb33ac8f56939cc582010ecf4d9c25d4 | patch -p1 -R > > > Rebuild Wine and test your program again. > When you're done testing, reset your tree to the latest Wine commit > > Code: > git reset --hard HEAD > > I suggest to expand the above by adding the following: > > Alternatively, you can also check if the bug was actually invoked by that commit without reverting suspected commit. For this, let's compare the behaviour of the program being tested right after and before this commit. To learn the program's conduct when the commit is in your Git, execute: > > Code: > > git checkout b821e839bb33ac8f56939cc582010ecf4d9c25d4 > > > > then compile Wine and test the program. The bug must be present. If this is the case, move next. > Switch the git tree to the state just before suspected commit by running (the "^" char means that the commit preceding b821e839bb33ac8f56939cc582010ecf4d9c25d4 is now a new detached HEAD): > > Code: > > git checkout b821e839bb33ac8f56939cc582010ecf4d9c25d4^ > > > > then rebuild Wine and see if the bug here. It must be gone away. If it's so, you have found the commit caused the bug! > The last step. Reset the HEAD to the original state: > > Code: > > git checkout origin > > > > In case after compilation you get non-working wine, clean up untracked files in the Git tree: > > Code: > > git clean -dfx > > > > Opinions?
