The idea behind git bisect is to perform a binary search in the history to find a particular regression. Imagine that you have the following development history: … — 0 — 1 — 2 — 3 — 4* — 5 — current You know that your program is not working properly at the current revision, … Read more
This will happen if the given good and bad revision are not direct descendants of each other. Let’s assume a repository like this (using exemplary names for the commits): * dffa2 good-commit * b38f4 a2 * cc19f a1 | * d1f17 bad-commit | * fbd1f b2 | * f66cc b1 |/ * 09f66 merge-base-commit What … Read more
I did some digging into the Git source code and found most of an answer myself… As of Git v1.6.4 (specifically, as of commit ebc9529f), Git uses “a PRNG (pseudo random number generator) with a bias” to determine which commit to try next after skipping one. I can’t say I follow the algorithm itself (which, … Read more
There is no easy way to accomplish this without further work. After playing with it for a little while I have something that might help you. git bisect start master f9d5924 for rev in $(git rev-list f9d5924..master –merges –first-parent); do git rev-list $rev^2 –not $rev^ done | xargs git bisect skip This starts git bisect … Read more
I thought of one possible solution, but I’m still hoping to find something more elegant: Mark all second-parents of all merges into the main branch as good Marking all remote parents of each merge as good will consider all the commits preceding them as good (and as such skipped by bisect). This solution should also … Read more
This is a very old but unanswered question. I decided to investigate, and found that I could show that the behavior of Git is different to what the question says it is. One explanation is that Git improved the algorithm for bisect, or that the questioner made a mistake in marking commits. I am trying … Read more
Looking at some commits in the project, I see one by Marcel M. Cary (marcel@oak.homeunix.org) He says in a commit (it happens to be about git-pull but I think it is relevant) “git pull” fails because POSIX shells have a notion of current working directory that is different from getcwd(). The shell stores this path … Read more
git bisect reset is the correct command. From the documentation: After a bisect session, to clean up the bisection state and return to the original HEAD, issue the following command: $ git bisect reset By default, this will return your tree to the commit that was checked out before git bisect start. (A new git … Read more
From the git-bisect documentation: Bisect log and bisect replay After having marked revisions as good or bad, issue the following command to show what has been done so far: $ git bisect log If you discover that you made a mistake in specifying the status of a revision, you can save the output of this … Read more
The idea behind git bisect is to perform a binary search in the history to find a particular regression. Imagine that you have the following development history: … — 0 — 1 — 2 — 3 — 4* — 5 — current You know that your program is not working properly at the current revision, … Read more