Comment # 3
on bug 98170
from Christian König
Bisecting means you try to figure out what patch introduced this bug. E.g. you know that 11.2.2 work and 12.0.1 is broken. So you checkout the source code from git and issue "git bisect start mesa-12.0.1 mesa-11.2.2". Now git has the list of changes between 11.2.2 and 12.0.1, so it jumps into the middle of that list of changes. You then compile mesa and see if this version still works. If it works you say "git bisect good" and git will jump another quarter to the end of the list, if it doesn't work you say "git bisect bad" and git will jump a quarter to the beginning of the list. This repeats until you figured out which commit caused the problem.
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
