summaryrefslogtreecommitdiff
path: root/contrib
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2017-10-18 14:20:43 +0900
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-10-18 14:20:43 +0900
commite3e3c6a43e7f36d507129909e49d54f1e8ad65e2 (patch)
treeb4ab435d592b835fcc4f0a637d0b758d1600c7cd /contrib
parentMerge branch 'jc/doc-checkout' into maint (diff)
parenttag: respect color.ui config (diff)
downloadtgif-e3e3c6a43e7f36d507129909e49d54f1e8ad65e2.tar.xz
Merge branch 'jk/ref-filter-colors-fix' into maint
This is the "theoretically more correct" approach of simply stepping back to the state before plumbing commands started paying attention to "color.ui" configuration variable. * jk/ref-filter-colors-fix: tag: respect color.ui config Revert "color: check color.ui in git_default_config()" Revert "t6006: drop "always" color config tests" Revert "color: make "always" the same as "auto" in config" color: make "always" the same as "auto" in config provide --color option for all ref-filter users t3205: use --color instead of color.branch=always t3203: drop "always" color test t6006: drop "always" color config tests t7502: use diff.noprefix for --verbose test t7508: use test_terminal for color output t3701: use test-terminal to collect color output t4015: prefer --color to -c color.diff=always test-terminal: set TERM=vt100
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions