http://bugs.winehq.org/show_bug.cgi?id=17050
--- Comment #10 from Nikolay Sivov bunglehead@gmail.com 2009-02-15 07:08:46 --- (In reply to comment #9)
hello,
I'm sorry for delayed response - regressiontesting took a long time, a VIA C3 1GHz needs 18hours for wine compilation ... ;)
anyway, heres my result:
34aa6b7002af0155c6f0cc31a013391b17f62eea is first bad commit commit 34aa6b7002af0155c6f0cc31a013391b17f62eea Author: Michael Karcher wine@mkarcher.dialup.fu-berlin.de Date: Sun Aug 17 19:03:24 2008 +0200
kernel32: Fix profile cache logic and don't cache new files.:040000 040000 bcd57dae0e716d362b63b03f1f659ca585c88c39 668cc4a9aea3fa63a863dbb9dcdeeb65ab4817ac M dlls
is there a way I can doublecheck if this commit is the bad one? the last four tests were good, this are my last "bad" one ...
You could 'git revert' it, then build again and test.