diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2007-04-07 10:18:10 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2007-04-07 10:18:10 +0000 |
| commit | 12a3a233f89942d86ddf8c57697a2c2486c07f11 (patch) | |
| tree | d6b9602dc76fbd0d707ba8dd594d47b8b56a7929 /git-bisect.html | |
| parent | 5678d690dfb3a08e15be4d4b7545053724543047 (diff) | |
| download | git-htmldocs-12a3a233f89942d86ddf8c57697a2c2486c07f11.tar.gz | |
Autogenerated HTML docs for v1.5.1-81-gee969
Diffstat (limited to 'git-bisect.html')
| -rw-r--r-- | git-bisect.html | 18 |
1 files changed, 14 insertions, 4 deletions
diff --git a/git-bisect.html b/git-bisect.html index 538946d63..689679452 100644 --- a/git-bisect.html +++ b/git-bisect.html @@ -280,7 +280,7 @@ git-bisect(1) Manual Page on the subcommand:</p>
<div class="literalblock">
<div class="content">
-<pre><tt>git bisect start [<paths>...]
+<pre><tt>git bisect start [<bad> [<good>...]] [--] [<paths>...]
git bisect bad <rev>
git bisect good <rev>
git bisect reset [<branch>]
@@ -372,13 +372,23 @@ $ git reset --hard HEAD~3 # try 3 revs before what </div></div>
<p>Then compile and test the one you chose to try. After that, tell
bisect what the result was as usual.</p>
-<h3>Cutting down bisection by giving path parameter to bisect start</h3>
+<h3>Cutting down bisection by giving more parameters to bisect start</h3>
<p>You can further cut down the number of trials if you know what part of
the tree is involved in the problem you are tracking down, by giving
paths parameters when you say <tt>bisect start</tt>, like this:</p>
<div class="listingblock">
<div class="content">
-<pre><tt>$ git bisect start arch/i386 include/asm-i386</tt></pre>
+<pre><tt>$ git bisect start -- arch/i386 include/asm-i386</tt></pre>
+</div></div>
+<p>If you know beforehand more than one good commits, you can narrow the
+bisect space down without doing the whole tree checkout every time you
+give good commits. You give the bad revision immediately after <tt>start</tt>
+and then you give all the good revisions you have:</p>
+<div class="listingblock">
+<div class="content">
+<pre><tt>$ git bisect start v2.6.20-rc6 v2.6.20-rc4 v2.6.20-rc1 --
+ # v2.6.20-rc6 is bad
+ # v2.6.20-rc4 and v2.6.20-rc1 are good</tt></pre>
</div></div>
<h3>Bisect run</h3>
<p>If you have a script that can tell if the current source code is good
@@ -421,7 +431,7 @@ know the outcome.</p> </div>
<div id="footer">
<div id="footer-text">
-Last updated 04-Apr-2007 18:33:26 UTC
+Last updated 07-Apr-2007 10:17:28 UTC
</div>
</div>
</body>
|