On Thu, Jul 9, 2009 at 2:36 PM, Jasin
Colegrove<j.wholesalesupply@xxxxxxxxx> wrote:
> When running git bisect it keeps building 2.6.29-rc kernels. I thought
> v2.6.29 was in the future compared to 2.6.29-rc7 for example.
> running the command git bisect start v2.6.29-rc7 v2.6.29 disagrees
> though and tells me.
>
> It co's a commit somewhere around 2.6.29-rc7 which ultimately was a
> bad commit. Am I misunderstanding how this all works? Sorry to be a
> pain
That confuses everyone the first time. Basically the way it works
is that a commit that was authored before 2.6.29 will still be checked
since it was only merged in 2.6.29.
+--- B -- D -+
/ \
-- A -- C ---- E -- F -- G
e.g. in the above graph, imagine E is 2.6.29 and G is 2.6.30. Commits
B and D were written from a base of 2.6.29-rc6 (say) but merged at time
F between 2.6.29 and 2.6.30. The bisect will check both parents of F if
it needs to since that's when it actually hit the mainline.
--
Bob Copeland %% www.bobcopeland.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
