https://bugs.freedesktop.org/show_bug.cgi?id=29384 --- Comment #10 from Alex Deucher <agd5f@xxxxxxxxx> 2010-08-03 11:56:42 PDT --- (In reply to comment #9) > I am awfully sorry, but I am not familiar with git/git-bitsect. > Of course I will try every patch you can over and give you as much as possible > details about the effect. It's very easy. Assuming you have a git tree checked out: git bisect start git bisect good v2.6.34 git bisect bad v2.6.35 After that git will walk you through the rest. It will check out the appropriate commit, at which point you can compile it, test it, and if it's good, run: git bisect good and if it's bad: git bisect bad and git will select the next commit and the process continues. If there is a commit that doesn't boot or build, you can skip it with: git bisect skip See this page for more info: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
