@@ -20,7 +20,7 @@ on the subcommand:
20
20
git bisect bad [<rev>]
21
21
git bisect good [<rev>...]
22
22
git bisect skip [(<rev>|<range>)...]
23
- git bisect reset [<branch >]
23
+ git bisect reset [<commit >]
24
24
git bisect visualize
25
25
git bisect replay <logfile>
26
26
git bisect log
@@ -81,16 +81,27 @@ will have been left with the first bad kernel revision in "refs/bisect/bad".
81
81
Bisect reset
82
82
~~~~~~~~~~~~
83
83
84
- To return to the original head after a bisect session, issue the
85
- following command:
84
+ After a bisect session, to clean up the bisection state and return to
85
+ the original HEAD, issue the following command:
86
86
87
87
------------------------------------------------
88
88
$ git bisect reset
89
89
------------------------------------------------
90
90
91
- This resets the tree to the original branch instead of being on the
92
- bisection commit ("git bisect start" will also do that, as it resets
93
- the bisection state).
91
+ By default, this will return your tree to the commit that was checked
92
+ out before `git bisect start`. (A new `git bisect start` will also do
93
+ that, as it cleans up the old bisection state.)
94
+
95
+ With an optional argument, you can return to a different commit
96
+ instead:
97
+
98
+ ------------------------------------------------
99
+ $ git bisect reset <commit>
100
+ ------------------------------------------------
101
+
102
+ For example, `git bisect reset HEAD` will leave you on the current
103
+ bisection commit and avoid switching commits at all, while `git bisect
104
+ reset bisect/bad` will check out the first bad revision.
94
105
95
106
Bisect visualize
96
107
~~~~~~~~~~~~~~~~
0 commit comments