The bisect code was a bit confused, and would always look at the versions at the boundaries, instead of the versions in the middle, thus not doing a proper bisect. This change fixes this behaviour, the revision tested will be in the middle of the current range, and will then become the lower (for a good revision) or upper (for a bad revision) boundary for the next iteration. |
||
---|---|---|
README.md | ||
repo-bisect |
README.md
This is a collection of tools to make working with repo easier
repo-bisect
Similar to git bisect, but works with an entire repo.
Note that due to the way certain code review tools like gerrit work, the git committer date may reflect when commits are uploaded for review rather than when they are actually introduced into the project.