From: Jeff King <peff@peff.net>
To: Andrew Klotz via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Andrew Klotz <agc.klotz@gmail.com>
Subject: Re: [PATCH 1/2] config: improve error message for boolean config
Date: Fri, 18 Sep 2020 14:10:26 -0400 [thread overview]
Message-ID: <20200918181026.GA187490@coredump.intra.peff.net> (raw)
In-Reply-To: <689d84672422dd96d1eb89ea6137e79ce4030248.1600395427.git.gitgitgadget@gmail.com>
On Fri, Sep 18, 2020 at 02:17:06AM +0000, Andrew Klotz via GitGitGadget wrote:
> diff --git a/t/t0205-gettext-poison.sh b/t/t0205-gettext-poison.sh
> index f9fa16ad83..b66d34c6f2 100755
> --- a/t/t0205-gettext-poison.sh
> +++ b/t/t0205-gettext-poison.sh
> @@ -33,7 +33,7 @@ test_expect_success 'eval_gettext: our eval_gettext() fallback has poison semant
>
> test_expect_success "gettext: invalid GIT_TEST_GETTEXT_POISON value doesn't infinitely loop" "
> test_must_fail env GIT_TEST_GETTEXT_POISON=xyz git version 2>error &&
> - grep \"fatal: bad numeric config value 'xyz' for 'GIT_TEST_GETTEXT_POISON': invalid unit\" error
> + grep \"fatal: bad boolean config value 'xyz' for 'GIT_TEST_GETTEXT_POISON'\" error
> "
This test is pretty subtle and depends on gettext-poison's inner
workings. I wonder if it's worth adding a separate:
git config --bool --default=foo does.not.exist
test in t1300 or similar.
-Peff
next prev parent reply other threads:[~2020-09-18 18:10 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 [this message]
2020-09-18 18:30 ` Phillip Wood
2020-09-18 19:14 ` Junio C Hamano
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=20200918181026.GA187490@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=agc.klotz@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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).