In some cases during a git bisect session, testing a particular commit takes quite long (for instance, because I have to build a full release package and deploy it on a particularly strange machine). In fact, testing a build takes so long that I'd like to start building the next two commits already without knowing whether the current test succeeds or not. That way, I can speed up bisecting by testing the current version and build the next two versions in parallel.
Does anybody know a trick to make git bisect show the next two revisions, depending on whether the current commit is good or bad?
git bisect uses git rev-list --bisect internally to find out, which revision is the midpoint between two revisions. You can use it by yourself to basically reimplement git bisect. It shouldn't be that hard.