git/git-bisect.sh, branch v1.5.2

Bisect: simplify "bisect start" logging.

2007-04-17T04:44:40Z

Signed-off-by: Christian Couder Signed-off-by: Junio C Hamano

git-bisect: allow bisecting with only one bad commit.

2007-04-07T00:55:57Z

This allows you to say: git bisect start git bisect bad $bad git bisect next to start bisection without knowing a good commit. This would have you try a commit that is half-way since the beginning of the history, which is rather wasteful if you already know a good commit, but if you don't (or your history is short enough that you do not care), there is no reason not to allow this. Signed-off-by: Junio C Hamano

git-bisect: modernization

2007-04-06T05:51:14Z

This slightly modernizes the bisect script to use show-ref/for-each-ref instead of looking into $GIT_DIR/refs files directly. Signed-off-by: Junio C Hamano

Bisect: teach "bisect start" to optionally use one bad and many good revs.

2007-04-05T22:13:14Z

One bad commit is fundamentally needed for bisect to run, and if we beforehand know more good commits, we can narrow the bisect space down without doing the whole tree checkout every time we give good commits. This patch implements: git bisect start [ [...]] [--] [...] as a short-hand for this command sequence: git bisect start git bisect bad $bad git bisect good $good1 $good2... On the other hand, there may be some confusion between revs ( and ...) and ... if -- is not used and if an invalid rev or a pathspec that looks like a rev is given. Signed-off-by: Christian Couder Signed-off-by: Junio C Hamano

Bisect: Improve error message in "bisect_next_check".

2007-03-30T06:10:21Z

So we can remove the specific message in "bisect_run". Signed-off-by: Christian Couder Signed-off-by: Junio C Hamano

Bisect: add checks at the beginning of "git bisect run".

2007-03-27T19:48:30Z

We may be able to "run" with only one good revision given and then verify that the result of the first run is bad. And perhaps also the other way around. But for now let's check that we have at least one bad and one good revision before we start to run. Signed-off-by: Christian Couder Signed-off-by: Junio C Hamano

Bisect: Use "git-show-ref --verify" when reseting.

2007-03-26T06:14:06Z

Signed-off-by: Christian Couder Signed-off-by: Junio C Hamano

git-bisect.sh: properly dq $GIT_DIR

2007-03-23T20:29:55Z

Otherwise you would be in trouble if your GIT_DIR has IFS letters in it. Signed-off-by: Junio C Hamano

git-bisect: typofix

2007-03-23T20:15:21Z

The branch you are on while bisecting is always "bisect", and checking for "refs/heads/bisect*" is wrong. Only check if it is exactly "refs/heads/bisect". Signed-off-by: Junio C Hamano

Bisect: implement "git bisect run ..." to automatically bisect.

2007-03-23T08:54:47Z

This idea was suggested by Bill Lear (Message-ID: <17920.38942.364466.642979@lisa.zopyra.com>) and I think it is a very good one. This patch adds a new test file for "git bisect run", but there is currently only one basic test. Signed-off-by: Christian Couder Signed-off-by: Junio C Hamano