This problem still occurs on kernel 2.6.37-git4.
Is there a way to do a git-bisect when a particular commit is removed?
When I did a
git reset --hard v2.6.37
git revert 541cc966915b6756e54c20eebe60ae957afdb537
and rebuilt the kernel I still had the problem, indicating that some
other commit in addition to 541cc966915b6756e54c20eebe60ae957afdb537 was
causing problems.
Arthur.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d2a6464.3070...@internode.on.net
