summaryrefslogtreecommitdiff
path: root/sha1_file.c
diff options
context:
space:
mode:
authorChristian Couder <christian.couder@gmail.com>2017-01-13 15:44:05 +0100
committerJunio C Hamano <gitster@pobox.com>2017-01-13 11:15:38 -0800
commit3f05402ac00ed6415b1df2b6823471e017817432 (patch)
treef5e30067e20ec34f5667fd3c0c85201309d63be6 /sha1_file.c
parent06e6a745064c4f2f827177f6d92f4b9adb018200 (diff)
downloadgit-ad/bisect-terms.tar.gz
Documentation/bisect: improve on (bad|new) and (good|bad)ad/bisect-terms
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 'sha1_file.c')
0 files changed, 0 insertions, 0 deletions