On Sat, Jun 7, 2008 at 3:49 PM, gedgeck <wineforum-user@xxxxxxxxxx> wrote: > > austin987 wrote: >> On Sat, Jun 7, 2008 at 3:17 PM, gedgeck <wineforum-user@xxxxxxxxxx> wrote: >> >> > >> > >> > > Please run a regression test: >> > > http://wiki.winehq.org/RegressionTesting >> > > >> > >> > >> > Well, I am done regression test. I used wine-0.9.50 as "good" and wine-0.9.59 as "bad". All of ten tests show that bug is at first half of patches and finally I get message that: >> > >> > Bisecting: 0 revisions left to test after this >> > >> > and any strings like "a460a2df43aa8eae10b1db028c6020829b009c54 is first bad commit". From RegresionTesting How to I'm not understand what I need to do next and what means that result. So please tell me my next step. >> > >> > >> > >> > >> > >> > >> > >> >> It should tell you the first bad commit. Once it does, post that >> information here. > > > Sorry, after message about none revisions left to test... I type again 'git bisect bad' and got next: > Code: > > 29d66b48ef1f3ed3519fb020260086c8d3aba1a6 is first bad commit > commit 29d66b48ef1f3ed3519fb020260086c8d3aba1a6 > Author: Jacek Caban <jacek@xxxxxxxxxxxxxxx> > Date: Fri Nov 30 13:32:56 2007 +0100 > > mshtml: Added IHTMLElement2::get_dir implementation. > > :040000 040000 08f95dcc0c71f8ec9e80970d166ead59f19e8977 801bf15bc9323ff88d3c4942896b1855a88a2430 M dlls > > > Is it positive result? > > > > > > Doesn't sound like that patch should affect it. Try running the test again.
