dimesio wrote: > > What did you set as git bisect good and git bisect bad? According to the bug report, this regression happened somewhere between 1.1.36 and 1.1.38, so you shouldn't have anywhere near that many revisions to test, not even from the start. When I set those two versions as good and bad, git tells me there are 373 revisions left to test. > > You're not done until git tells you "[commit number] is first bad commit." > > You need to reread the instructions for regression testing. http://wiki.winehq.org/RegressionTesting Okay, I go to try again. Is hard to me, the explanation in RegressionTesting page are short for me. Example: I not understand how git "know" where is the 1.1.44 version and where the 1.2, ecause I use separate folders I think I need found any good manual in spanish about use git.
