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

chriscool · gitster · commit 3f05402ac00e · 2017-01-13T11:15:38.000-08:00
The following part of the description:

git bisect (bad|new) [&lt;rev&gt;]
git bisect (good|old) [&lt;rev&gt;...]

may be a bit confusing, as a reader may wonder if instead it should be:

git bisect (bad|good) [&lt;rev&gt;]
git bisect (old|new) [&lt;rev&gt;...]

Of course the difference between "[&lt;rev&gt;]" and "[&lt;rev&gt;...]" should hint
that there is a good reason for the way it is.

But we can further clarify and complete the description by adding
"&lt;term-new&gt;" and "&lt;term-old&gt;" to the "bad|new" and "good|old"
alternatives.

Signed-off-by: Christian Couder &lt;chriscool@tuxfamily.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
@@ -18,8 +18,8 @@ on the subcommand:
 
  git bisect start [--term-{old,good}=<term> --term-{new,bad}=<term>]
 		  [--no-checkout] [<bad> [<good>...]] [--] [<paths>...]
- git bisect (bad|new) [<rev>]
- git bisect (good|old) [<rev>...]
+ git bisect (bad|new|<term-new>) [<rev>]
+ git bisect (good|old|<term-old>) [<rev>...]
  git bisect terms [--term-good | --term-bad]
  git bisect skip [(<rev>|<range>)...]
  git bisect reset [<commit>]
