http://bugs.winehq.org/show_bug.cgi?id=15377
--- Comment #9 from Ben Trusty ben.trusty@gmail.com 2008-09-22 21:42:28 --- (In reply to comment #8)
No, you don't use git bisect reset *at all* until the entire process is completely finished. I only brought it up because you could've saved yourself a lot of time. Just follow the directions on that site...it's not that hard.
i just listed what i thought the site was the order of operations
the site http://wiki.winehq.org/RegressionTesting has a whole list of "what ifs" added into the order of operations if there is an easier list, that would be helpful, as what i just posted was the order of what i was supposed to do.
b/c i did initially what i thought was done and got to a point that said
THEN YOU ARE NOT DONE YET!
Once that patch is identified, post this info into bugzilla in the bug report (assuming one is opened, if not, open one). Also be sure to add the author of the patch to the CC. This information will allow the developers to fix the problem much quicker.
post this info into bugzilla in the bug report (assuming one is opened, if not, open one)
so i did that, which oddly there is something AFTER that (e.g. git bisect reset), something i did AFTER i had completed and had some feedback from the process (e.g. what i posted that the problem was which was causing the game to not function in 1.1.5