From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: Felipe Contreras <felipe.contreras@gmail.com>
Subject: [PATCH 2/3] git config: clarify bool types
Date: Sun, 11 Oct 2009 23:46:12 +0300 [thread overview]
Message-ID: <1255293973-17444-3-git-send-email-felipe.contreras@gmail.com> (raw)
In-Reply-To: <1255293973-17444-2-git-send-email-felipe.contreras@gmail.com>
The value is what it is, the --bool and --bool-or-int options don't
specify the value type, just how it is interpreted. For example: a value
of '1' can be interpreted as 'true'.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---
builtin-config.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/builtin-config.c b/builtin-config.c
index a2d656e..29d7b75 100644
--- a/builtin-config.c
+++ b/builtin-config.c
@@ -66,9 +66,9 @@ static struct option builtin_config_options[] = {
OPT_STRING(0, "get-color", &get_color_slot, "slot", "find the color configured: [default]"),
OPT_STRING(0, "get-colorbool", &get_colorbool_slot, "slot", "find the color setting: [stdout-is-tty]"),
OPT_GROUP("Type"),
- OPT_BIT(0, "bool", &types, "value is \"true\" or \"false\"", TYPE_BOOL),
+ OPT_BIT(0, "bool", &types, "value is intepreted as bool (\"true\" or \"false\")", TYPE_BOOL),
OPT_BIT(0, "int", &types, "value is decimal number", TYPE_INT),
- OPT_BIT(0, "bool-or-int", &types, "value is --bool or --int", TYPE_BOOL_OR_INT),
+ OPT_BIT(0, "bool-or-int", &types, "value is interpreted either as bool or int", TYPE_BOOL_OR_INT),
OPT_GROUP("Other"),
OPT_BOOLEAN('z', "null", &end_null, "terminate values with NUL byte"),
OPT_END(),
--
1.6.5.4.g31fc3
next prev parent reply other threads:[~2009-10-11 20:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 20:46 [PATCH 0/3] Trivial patches Felipe Contreras
2009-10-11 20:46 ` [PATCH 1/3] Fix a bunch of pointer declarations (codestyle) Felipe Contreras
2009-10-11 20:46 ` Felipe Contreras [this message]
2009-10-11 20:46 ` [PATCH 3/3] user-manual: use 'fast-forward' Felipe Contreras
2009-10-12 5:05 ` Junio C Hamano
2009-10-12 10:05 ` Felipe Contreras
2009-10-12 12:50 ` Michael J Gruber
2009-10-12 5:01 ` [PATCH 2/3] git config: clarify bool types Junio C Hamano
2009-10-12 10:03 ` Felipe Contreras
2009-10-12 12:30 ` Michael J Gruber
2009-10-12 17:14 ` Felipe Contreras
2009-10-13 7:09 ` Michael J Gruber
2009-10-13 10:02 ` Felipe Contreras
2009-10-11 20:53 ` [PATCH 1/3] Fix a bunch of pointer declarations (codestyle) Thiago Farina
2009-10-11 20:56 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1255293973-17444-3-git-send-email-felipe.contreras@gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).