author | Christian Couder <chriscool@tuxfamily.org> | |
Wed, 4 Apr 2007 05:12:02 +0000 (07:12 +0200) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Thu, 5 Apr 2007 22:13:14 +0000 (15:13 -0700) | ||
commit | 38a47fd6e316030ba1e72ea447243cb47adf2505 | |
tree | 365abc710b3f7ad43bc2cb70c590a500eeeb85e0 | tree | snapshot |
parent | 33580fbd308593e36395926fd35b501976ad322a | commit | diff |
Bisect: teach "bisect start" to optionally use one bad and many good revs.
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 [<bad> [<good>...]] [--] [<pathspec>...]
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
(<bad> and <good>...) and <pathspec>... if -- is not used
and if an invalid rev or a pathspec that looks like a rev is
given.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
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 [<bad> [<good>...]] [--] [<pathspec>...]
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
(<bad> and <good>...) and <pathspec>... if -- is not used
and if an invalid rev or a pathspec that looks like a rev is
given.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-bisect.sh | diff | blob | history | |
t/t6030-bisect-run.sh | diff | blob | history |