bisect: document "terms" subcommand more fully
The documentation for "git bisect terms", although it did not hide any information, was a bit incomplete and forced readers to fill in the blanks to get the complete picture. Acked-by: Matthieu Moy <git@matthieu-moy.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Feb 7, 2024 at 13:44 UTC
47ac5f6e1a0125965f6907dc55c130615cf131e1
1 file changed
+5
-3
Documentation/git-bisect.txt
+5
-3
@@ -20,7 +20,7 @@ on the subcommand:
20
[--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<paths>...]
21
git bisect (bad|new|<term-new>) [<rev>]
22
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)]
24
git bisect skip [(<rev>|<range>)...]
25
git bisect reset [<commit>]
26
git bisect (visualize|view)
@@ -165,8 +165,10 @@ To get a reminder of the currently used terms, use
165
git bisect terms
166
------------------------------------------------
167
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.
172
173
If you would like to use your own terms instead of "bad"/"good" or
174
"new"/"old", you can choose any names you like (except existing bisect