Finding a kernel regression in half an hour with git bisect run (2018)
We used to have to do this a lot on my team at Google, except with Google tools (piper and blaze).  The difference is that because Google is a monorepo, you often end up with 50K+changes to sort through, at which the log2 propertyy of bisection becomes necessary, not just convenient.