From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Andrew Klotz via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Andrew Klotz <agc.klotz@gmail.com>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH 1/2] config: improve error message for boolean config
Date: Fri, 18 Sep 2020 12:14:38 -0700 [thread overview]
Message-ID: <xmqqpn6ilwwx.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <15b794ad-6eae-6de1-3328-9b814e8e2605@gmail.com> (Phillip Wood's message of "Fri, 18 Sep 2020 19:30:59 +0100")
Phillip Wood <phillip.wood123@gmail.com> writes:
> This patch improves things for boolean config keys but
> git_config_bool_or_int() is used by status.submoduleSummary, merge.log
> and commit.verbose which can be either a number or a boolean (where a
> boolean generally means use a default number).
Excellent point. The rephrasing done by the patch as-is will be a
regression.
> It would be a more
> invasive change but I wonder if it would be better for
> git_config_bool() to have it's own error message rather sharing it
> with git_config_bool_or_int().
You'd probably need a variant of die_bad_numer(), with an untested
patch like below.
config.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/config.c b/config.c
index 8db9c77098..801d944d2b 100644
--- a/config.c
+++ b/config.c
@@ -1097,7 +1097,10 @@ int git_config_bool_or_int(const char *name, const char *value, int *is_bool)
return v;
}
*is_bool = 0;
- return git_config_int(name, value);
+
+ if (!git_parse_int(value, &v))
+ die_bad_number_or_bool(name, value);
+ return v;
}
int git_config_bool(const char *name, const char *value)
next prev parent reply other threads:[~2020-09-18 19:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 2:17 [PATCH 0/2] config: improve error message for boolean config Andrew Klotz via GitGitGadget
2020-09-18 2:17 ` [PATCH 1/2] " Andrew Klotz via GitGitGadget
2020-09-18 18:10 ` Jeff King
2020-09-18 18:30 ` Phillip Wood
2020-09-18 19:14 ` Junio C Hamano [this message]
2020-09-18 2:17 ` [PATCH 2/2] formatting for error messages Andrew Klotz via GitGitGadget
2020-09-18 17:22 ` [PATCH 0/2] config: improve error message for boolean config Junio C Hamano
2021-02-09 1:25 ` [PATCH v2] " Andrew Klotz via GitGitGadget
2021-02-09 16:51 ` Jeff King
2021-02-09 21:02 ` Junio C Hamano
2021-02-11 20:30 ` [PATCH v3] " Andrew Klotz via GitGitGadget
2021-02-12 10:38 ` Jeff King
2021-02-12 19:52 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2021-01-23 23:15 [PATCH 1/2] " Andrew Klotz
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqpn6ilwwx.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=agc.klotz@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=peff@peff.net \
--cc=phillip.wood123@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).