Re: [PATCH v4 3/3] config: add '--show-origin' option to print the origin of a config value
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 15, 2016, 22:18 UTC
- Message-ID
- <xmqqegcdpqhh.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <1455531466-16617-4-git-send-email-larsxschneider@gmail.com>
larsxschneider@gmail.com writes:
Show 15 quoted lines
> +test_expect_success 'set up custom config file' ' > + CUSTOM_CONFIG_FILE=$(printf "file\twith\ttabs.conf") && > + cat >"$CUSTOM_CONFIG_FILE" <<-\EOF > + [user] > + custom = true > + EOF > +' > + > +test_expect_success '--show-origin escape special file name characters' ' > + cat >expect <<-\EOF && > + file:"file\twith\ttabs.conf" user.custom=true > + EOF > + git config --file "$CUSTOM_CONFIG_FILE" --show-origin --list >output && > + test_cmp expect output > +'
Do we really need to use a file with such a name?
An existing test t3300 tells me that a test that uses a path with a tab needs to be skipped on FAT/NTFS. If your goal is to make sure dquote is exercised, can't we just do with a path with a SP in it or something?
Thanks.