git practices

[Peter Harris]

Jeremy Huddleston wrote:
>   I'm not even sure how bisection
> in git works without a linear model.  My guess is that it just bisects
> along the main branch and sees the merge commit as a single

Git doesn't know which branch is 'main'. But that's okay. Git bisects
the DAG, not any particular linear commit chain.

This can be surprising if you're not expecting it. For example, if you
have two roughly equal length branches that you just merged, bisecting
just before the branch to just after the merge will likely choose a
commit right before the merge, only a few commits back in the history.
But this is good because testing that commit will eliminate one of the
branches (and therefore half of the commits), and then git will bisect
the other one the way you'd expect.

Peter Harris
-- 
               Open Text Connectivity Solutions Group
Peter Harris                    http://www.opentext.com/connectivity
Research and Development        Phone: +1 905 762 6001
pharris at opentext.com            Toll Free: 1 877 359 4866