Comment # 9
on bug 109135
from Alex Deucher
(In reply to rmuncrief from comment #8) > (In reply to Alex Deucher from comment #7) > > Can you bisect to figure out what commit broke things for you? > > Actually I remember doing that many years ago when I was a maintainer for > Steam under wine. I'll look and see if I can find a current bisect tutorial > and give it a try. Any links or tips you can give to help give me a quick > start would be appreciated. I do remember it can take many days, which I'm > willing to invest as I said. However the fewer days the better! :) It's pretty straight forward. Just google for "kernel git bisect howto".
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
