Skip to content

Commit 1e73351

Browse files
committed
Merge branch 'jc/bisect-doc' into maint-2.43
Doc update. * jc/bisect-doc: bisect: document command line arguments for "bisect start" bisect: document "terms" subcommand more fully
2 parents 8d792dc + 841dbd4 commit 1e73351

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

Documentation/git-bisect.txt

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,11 +16,11 @@ DESCRIPTION
1616
The command takes various subcommands, and different options depending
1717
on the subcommand:
1818

19-
git bisect start [--term-(new|bad)=<term-new> --term-(old|good)=<term-old>]
19+
git bisect start [--term-(bad|new)=<term-new> --term-(good|old)=<term-old>]
2020
[--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<paths>...]
2121
git bisect (bad|new|<term-new>) [<rev>]
2222
git bisect (good|old|<term-old>) [<rev>...]
23-
git bisect terms [--term-good | --term-bad]
23+
git bisect terms [--term-(good|old) | --term-(bad|new)]
2424
git bisect skip [(<rev>|<range>)...]
2525
git bisect reset [<commit>]
2626
git bisect (visualize|view)
@@ -165,8 +165,10 @@ To get a reminder of the currently used terms, use
165165
git bisect terms
166166
------------------------------------------------
167167

168-
You can get just the old (respectively new) term with `git bisect terms
169-
--term-old` or `git bisect terms --term-good`.
168+
You can get just the old term with `git bisect terms --term-old`
169+
or `git bisect terms --term-good`; `git bisect terms --term-new`
170+
and `git bisect terms --term-bad` can be used to learn how to call
171+
the commits more recent than the sought change.
170172

171173
If you would like to use your own terms instead of "bad"/"good" or
172174
"new"/"old", you can choose any names you like (except existing bisect

0 commit comments

Comments
 (0)