Documentation/bisect: improve on (bad|new) and (good|bad)

The following part of the description: git bisect (bad|new) [<rev>] git bisect (good|old) [<rev>...] may be a bit confusing, as a reader may wonder if instead it should be: git bisect (bad|good) [<rev>] git bisect (old|new) [<rev>...] Of course the difference between "[<rev>]" and "[<rev>...]" should hint that there is a good reason for the way it is. But we can further clarify and complete the description by adding "<term-new>" and "<term-old>" to the "bad|new" and "good|old" alternatives. Signed-off-by: Christian Couder <chriscool@tuxfamily.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Christian Couder committed Jan 13, 2017 at 15:44 UTC 3f05402ac00ed6415b1df2b6823471e017817432
1 file changed +2 -2
Documentation/git-bisect.txt
+2 -2
@@ -18,8 +18,8 @@ on the subcommand:
18
19 git bisect start [--term-{old,good}=<term> --term-{new,bad}=<term>]
20 [--no-checkout] [<bad> [<good>...]] [--] [<paths>...]
21 - git bisect (bad|new) [<rev>]
22 - git bisect (good|old) [<rev>...]
21 + git bisect (bad|new|<term-new>) [<rev>]
22 + git bisect (good|old|<term-old>) [<rev>...]
23 git bisect terms [--term-good | --term-bad]
24 git bisect skip [(<rev>|<range>)...]
25 git bisect reset [<commit>]