summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2009-04-09 19:40:39 (GMT)
committerJunio C Hamano <gitster@pobox.com>2009-04-11 18:00:45 (GMT)
commit8f8c6fafd92fd547547bd7735e2d121a20997703 (patch)
tree42659ac556b9b826d48a165f2f6260d6e2f36e6b
parente37347bba651f051998f23a3701b555f1a194557 (diff)
downloadgit-8f8c6fafd92fd547547bd7735e2d121a20997703.zip
git-8f8c6fafd92fd547547bd7735e2d121a20997703.tar.gz
git-8f8c6fafd92fd547547bd7735e2d121a20997703.tar.bz2
Allow users to un-configure rename detection
On Thu, 9 Apr 2009, Linus Torvalds wrote: > > [diff] > renames = no Btw, while doing this, I also though that "renames = on/off" made more sense, but while we allow yes/no and true/false for booleans, we don't allow on/off. Should we? Maybe. Here's a stupid patch. Linus Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--config.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/config.c b/config.c
index b76fe4c..e7d91f5 100644
--- a/config.c
+++ b/config.c
@@ -331,9 +331,9 @@ int git_config_bool_or_int(const char *name, const char *value, int *is_bool)
return 1;
if (!*value)
return 0;
- if (!strcasecmp(value, "true") || !strcasecmp(value, "yes"))
+ if (!strcasecmp(value, "true") || !strcasecmp(value, "yes") || !strcasecmp(value, "on"))
return 1;
- if (!strcasecmp(value, "false") || !strcasecmp(value, "no"))
+ if (!strcasecmp(value, "false") || !strcasecmp(value, "no") || !strcasecmp(value, "off"))
return 0;
*is_bool = 0;
return git_config_int(name, value);