Sebastian Hofmann wrote:
> Brice Goglin wrote:
>
>> Does your "2.3.1 log" below mean "latest upstream git"?
>>
>
> I think so. I am not familiar with git - I did the following:
>
> git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel
> ./autogen.sh
> make
>
And make install into the right directory, right ? (or cp intel_drv.so ...)
>> It would be great if you could check that 2.2.0 worked fine (it's on
>> snapshot.debian.net) and then do a git-bisect between 2.2.0 and 2.3.0 to
>> find the breaking commit. If you need help to do so, please let me know.
>>
>
> Please tell me how to do it...
>
If 2.3.0 is broken and 2.2.0 works fine, you should do:
git bisect start
git bisect good xf86-video-intel-2.2.0
git bisect bad xf86-video-intel-2.3.0
Then git will choose a commit to test (in the middle of the above
range). Run autogen, make and make install. If it works, you run "git
bisect good", if it breaks, run "git bisect bad". Git will propose
another commit in the middle of the remaining range. Do the same test,
... again and again until git finds the exact commit breaking things.
When it is done, git bisect --reset
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
