There are actually two possible global configuration files,
`$HOME/.gitconfig` and `$XDG_CONFIG_HOME/git/config`. However, the
`--global` file by default modifies only the former if it's present.
Add a `--file` option to `git lfs install` and `git lfs uninstall` so
that users can choose which of those files they'd like to use.
Update several tests to deal with our new, simpler error message so we
can avoid having to produce a huge number of different error messages.
We convert a few messages output by the various commands to use
the capitalized "Git" project name instead of the lowercase variant,
which will make them consistent with how the Git project name appears
in other messages elsewhere.
Note that some of these messages are not yet passed as translation
strings, but we will address that issue in a subsequent commit.
In some of our worktree code, we use configuration options under the
extensions hierarchy. In upstream Git, unknown extensions are rejected
if the repository format version is 1; this format version is otherwise
identical to version 0.
Until recently, Git would accept extensions with a repository format
version of 0, but fail to reject unknown extensions. However, this
could cause serious problems with the repository, so it was recently
fixed to ignore all extensions in repository format 0.
These tests set extensions.worktreeConfig without setting the repository
format version, and consequently they fail with the latest versions of
Git. Let's set the version appropriately so that our tests continue to
work.
We add a number of tests, conditional on the Git version, to
validate the functionality of the --worktree option when
installing or uninstalling.
Note that because this simply passed through to the "git config"
command, we inherit the behaviour that --worktree functions
like --local when only a single, default working tree is in use.
And if we have a Git version older than 2.20.0, we confirm that
the --worktree option is not supported.
