http://bugs.winehq.org/show_bug.cgi?id=14978
--- Comment #8 from Reinhard Berger geist1@sms.at 2008-09-04 08:46:47 --- well, i've done again a regress test now from scratch.
I still wonder, why i get version 1.1.2 when i entered 1.1.1 at first good version ?
Anyway, this time it is completly diffrent.
Before i got always "bad" gits, this time i always get "good" ones, means the bug doesnt appear, but before the bug always appeart.
runnning now the steps down with git, it comes to a line like this :
geist@GST:~/Test/wine-git$ git bisect good de92617b3ec1501a2a56f6262d9653f502a5b331 is first bad commit commit de92617b3ec1501a2a56f6262d9653f502a5b331 Author: Alexandre Julliard julliard@winehq.org Date: Fri Aug 22 17:16:26 2008 +0200
Release 1.1.3.
:100644 100644 9b14216d945fc84716491e6fd145729a70b86d0c b692da069835e21f030e32323fc86dce98bef531 M ANNOUNCE :100644 100644 1c0a52802e105b9d8f4609ab38343d309aeabb81 ede4ec6e8477a48509842aff0c9bfc9c28c443dc M VERSION :100755 100755 4345d9501b3519a19e2d5e3f59639354a74b9ca2 66e0fd5f1d6f0956ad789cd924d31c8c3c911890 M configure
Acording to the wiki page, i have done a git bisect reset Switched to branch "master"
Now i should enter the version 1.1.3 as the first good one, i've done then :
git bisect good wine-1.1.3 git bisect bad wine-1.1.3
and now ? should i re-compile wine again ? or what should i do now ?
Trying to call another time "git bisect good" doesnt give out any messages anymore.