gistfile1.txt

hmm ok maybe I should bisect this bug

let's see if this has always happened

$ git checkout some-old-rev

nope it used to be good ok let's bisect

$ git bisect good
already bisecting

ah crap, I need to clear the old one

$ git bisect reset
okay

ok let's go

$ git bisect good
k

$ git checkout branch
already there

oh yeah I forgot git bisect reset also checks out things because why
have a command that does one distinct thing when you could glob a bunch
of functions together in a single command, right?

$ git bisect reset
ok

$ git bisect bad
k

ok now what was that ref I was at?  I'd probably remember
it if it were a nice number like hg but whatevs

$ git reflog
(giant mountain of crap)

hmm what order are these in?  are the recent revs at the head or tail?
this would be obvious if we used rev numbers like hg

(manually examine the last few entries, they don't look familiar)

$ git reflog | head

oh yeah that's the one I want

(manually copy the rev)

$ git checkout cmd-v

$ git bisect good

and we're off!