Re: git bisect selects commit outside initial bisect range?

[Andreas Schwab]

PaweÅ Sikora <pluto@xxxxxxxx> writes:

> i've started git bisect between good-v2.6.34 and bad-v2.6.35-rc1
> and after few steps git-bisect jumps to commit before v2.6.34.
>
> [~/src/linux/linux-2.6]$ make kernelrelease
> 2.6.34-rc6-00551-g7a6cb0d
>
> is it normal that bisect selects next step outside initial range?

It's not outside the range:

$ git rev-list v2.6.34..v2.6.35-rc1 | grep ^7a6cb0d
7a6cb0d5497418599d2125b670926b75e673861c

7a6cb0d is a commit in a branch reachable from v2.6.35-rc1 but not from
v2.6.34.

Andreas.

-- 
Andreas Schwab, schwab@xxxxxxxxxxxxxx
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/