summaryrefslogtreecommitdiff
path: root/builtin/branch.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2017-10-18 14:20:43 +0900
committerJunio C Hamano <gitster@pobox.com>2017-10-18 14:20:43 +0900
commite3e3c6a43e7f36d507129909e49d54f1e8ad65e2 (patch)
treeb4ab435d592b835fcc4f0a637d0b758d1600c7cd /builtin/branch.c
parent4e4a0c6e794f1f37ba7fa65e5e774b9d6c168afc (diff)
parentb521fd122865dca88b99d05344ec189d39efcefb (diff)
downloadgit-e3e3c6a43e7f36d507129909e49d54f1e8ad65e2.tar.gz
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 'builtin/branch.c')
-rw-r--r--builtin/branch.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/builtin/branch.c b/builtin/branch.c
index 2ea92a70b7..8f779b02b5 100644
--- a/builtin/branch.c
+++ b/builtin/branch.c
@@ -92,7 +92,7 @@ static int git_branch_config(const char *var, const char *value, void *cb)
return config_error_nonbool(var);
return color_parse(value, branch_colors[slot]);
}
- return git_default_config(var, value, cb);
+ return git_color_default_config(var, value, cb);
}
static const char *branch_get_color(enum color_branch ix)