diff options
author | Christian Couder <christian.couder@gmail.com> | 2017-01-13 15:44:05 +0100 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2017-01-13 11:15:38 -0800 |
commit | 3f05402ac00ed6415b1df2b6823471e017817432 (patch) | |
tree | f5e30067e20ec34f5667fd3c0c85201309d63be6 /t/t5503-tagfollow.sh | |
parent | bisect: allow setting any user-specified in 'git bisect start' (diff) | |
download | tgif-3f05402ac00ed6415b1df2b6823471e017817432.tar.xz |
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 't/t5503-tagfollow.sh')
0 files changed, 0 insertions, 0 deletions