Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
Documentation/bisect: improve on (bad|new) and (good|bad)
author
Christian Couder
<christian.couder@gmail.com>
Fri, 13 Jan 2017 14:44:05 +0000
(15:44 +0100)
committer
Junio C Hamano
<gitster@pobox.com>
Fri, 13 Jan 2017 19:15:38 +0000
(11:15 -0800)
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>
Documentation/git-bisect.txt
patch
|
blob
|
history
raw
|
patch
| inline |
side by side
(parent:
06e6a74
)
diff --git
a/Documentation/git-bisect.txt
b/Documentation/git-bisect.txt
index 2044fe6820e0507a6dcc1823f8fe3fce407e4d90..b35218adf0098d4bc1b8ad329b337d744cebd619 100644
(file)
--- 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>]