summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorChristian Couder <christian.couder@gmail.com>2017-01-13 14:44:05 (GMT)
committerJunio C Hamano <gitster@pobox.com>2017-01-13 19:15:38 (GMT)
commit3f05402ac00ed6415b1df2b6823471e017817432 (patch)
treef5e30067e20ec34f5667fd3c0c85201309d63be6 /Documentation
parent06e6a745064c4f2f827177f6d92f4b9adb018200 (diff)
downloadgit-3f05402ac00ed6415b1df2b6823471e017817432.zip
git-3f05402ac00ed6415b1df2b6823471e017817432.tar.gz
git-3f05402ac00ed6415b1df2b6823471e017817432.tar.bz2
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>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-bisect.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index 2044fe6..b35218a 100644
--- 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>]