On Wednesday 10 November 2010 08:46:40 Chris Wilson wrote:
Did so. I've started with v2.6.36 for bisect good and
f6614b7bb405a9b35dd28baea989a749492c46b2 for bisect bad (was HEAD) in this
case. Again I ended in 5c12a07e8073295ce8b57a822f811ac34e4f8420 as the first
bad commit. The regression was introduced there, as the commit before is fine.
If it was reverted, the regression should be fixed by this. But I don't find
neither the fix/revert nor the reintroduction of the regression.
regrards,
Johannes
--