summaryrefslogtreecommitdiff
path: root/contrib/completion
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2018-08-13 04:33:30 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-08-13 10:44:52 -0700
commit275267937bdbb8611e8872d64adebe7587c6fa5a (patch)
treeed238128eeb22ec7ce75c77f4915ebe047a6aef7 /contrib/completion
parentrange-diff: left-pad patch numbers (diff)
downloadtgif-275267937bdbb8611e8872d64adebe7587c6fa5a.tar.xz
range-diff: make --dual-color the default mode
After using this command extensively for the last two months, this developer came to the conclusion that even if the dual color mode still leaves a lot of room for confusion about what was actually changed, the non-dual color mode is substantially worse in that regard. Therefore, we really want to make the dual color mode the default. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/completion')
-rw-r--r--contrib/completion/git-completion.bash2
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index 3d4ec34323..d63d2dffd4 100644
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -1981,7 +1981,7 @@ _git_range_diff ()
case "$cur" in
--*)
__gitcomp "
- --creation-factor= --dual-color
+ --creation-factor= --no-dual-color
$__git_diff_common_options
"
return