Re: Reachability lists in git
Show 8 quoted lines
> Tracking down regressions. Bisection isn't perfect. Suppose a
> bisection run ends up saying that B is the first bad commit. It's easy
> enough to build B and test it, to verify that it really is bad.
>
> But to be sure that B introduced the fault, it would help to find the
> latest commit that doesn't include B's changes -- that is, the latest
> commit that B isn't reachable from (or the maximal elements in the set
> of all such commits).
Isn't that B^ (or B^ and B^2, if B is a merge)?
Jonathan Nieder <jrnieder@gmail.com>