From: Philip Oakley <philipoakley@iee.email>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: GitList <git@vger.kernel.org>
Subject: Re: [RFC PATCH v1] t/README: the test repo does not have global or system configs
Date: Wed, 16 Oct 2019 20:08:57 +0100 [thread overview]
Message-ID: <dc8afd1b-2e69-e54d-aee9-e5d6c4b729f5@iee.email> (raw)
In-Reply-To: <20191016164707.GW29845@szeder.dev>
On 16/10/2019 17:47, SZEDER Gábor wrote:
> On Wed, Oct 16, 2019 at 01:45:15PM +0100, Philip Oakley wrote:
>> Signed-off-by: Philip Oakley <philipoakley@iee.email>
>> ---
>>
>> While tring to get to grips with some Git-for-Windows config settings
>> for testing >4GiB files, I couldn't find any note in the readme about
>> the test system config file sources.
> The path of the system config file is determined at compile time, with
> no way to override it at runtime. Since we don't want external config
> files influencing our tests, the only choice we have is to ignore the
> system config file; that's why our test framework sets
> GIT_CONFIG_NOSYSTEM=1.
Thanks.
>> Is this the right place for the information, is it complete enough,
>> and is the default config template special?
>>
>> t/README | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/t/README b/t/README
>> index 60d5b77bcc..3daa1fa182 100644
>> --- a/t/README
>> +++ b/t/README
>> @@ -485,6 +485,9 @@ This test harness library does the following things:
>> the --root option documented above, and a '.stress-<N>' suffix
>> appended by the --stress option.
>>
>> + - The --global and --system config files are ignored, and
>> + a basic --local config is created in the tst repository.
> s/tst/test/
>
> However, note that the global config file isn't really ignored, but
> different. The path of the global config file depends on the values
> of the env variables $XDG_CONFIG_HOME and $HOME, and, again, to avoid
> external influences, our test framework unsets the former, and
> overrides the latter with HOME="$TRASH_DIRECTORY". IOW the global
> config file in our tests is '.../t/trash directory.t1234-foo/.gitconfig'.
Thanks
>> +
>> - Defines standard test helper functions for your scripts to
>> use. These functions are designed to make all scripts behave
>> consistently when command line arguments --verbose (or -v),
>> --
>> 2.23.0.windows.1.21.g947f504ebe8.dirty
>>
I'll revise the text with this clarifying information (rephrased to man
page style)
Philip
next prev parent reply other threads:[~2019-10-16 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 12:45 [RFC PATCH v1] t/README: the test repo does not have global or system configs Philip Oakley
2019-10-16 16:47 ` SZEDER Gábor
2019-10-16 19:08 ` Philip Oakley [this message]
2019-10-18 14:00 ` [PATCH v2] " Philip Oakley
2019-10-21 3:55 ` Junio C Hamano
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=dc8afd1b-2e69-e54d-aee9-e5d6c4b729f5@iee.email \
--to=philipoakley@iee.email \
--cc=git@vger.kernel.org \
--cc=szeder.dev@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).