Maybe that's a bit advanced topic to be in the newbies section but I place it in here because I am a newbie, and I think it is to a great extent a newbie question.

I'm doing a git bisect on the kernel trying to trace a commit that causes a bug.

the bug is supposed to be somewhere between v3.12.9 and v3.13

but when I run
I get

Now how does that make sense? isn't it supposed to get me to a commit that is in the middle between 3.12.9 and 3.13?
is 3.12 actually a commit in between and I just don't understand the numberings right?
am I doing something wrong?

okay, I found the answer here

Why does "git bisect" make me test versions outside the "good-bad" range?

The reason may be that some commits have been developed starting from a version before the "good" commit, and then merged after the "good" commit.

See http://thread.gmane.org/gmane.comp.v...67/focus=99977 for more explanations from Linus.