Robin Rosenberg <[email protected]> writes:
> I guess this isn't true either. Anyone has a better way of
> specifiying where the system wide config file is read from,
> or a user-parseable definition of $(prefix) ?
... the system-wide configuration file (typically
/etc/gitconfig), rather than the repository specific
configuration file (.git/config)
should be sufficient.
>
> -- robin
>
> ----- Ursprungligt meddelande -----
>> Signed-off-by: Robin Rosenberg <[email protected]>
>> ---
>> Documentation/git-config.txt | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/git-config.txt
>> b/Documentation/git-config.txt
>> index 9ae2508..3198d52 100644
>> --- a/Documentation/git-config.txt
>> +++ b/Documentation/git-config.txt
>> @@ -107,7 +107,8 @@ See also <<FILES>>.
>>
>> --system::
>> For writing options: write to system-wide $(prefix)/etc/gitconfig
>> - rather than the repository .git/config.
>> + rather than the repository .git/config. However, $(prefix) is /usr
>> + then /etc/gitconfig is used.
>> +
>> For reading options: read only from system-wide
>> $(prefix)/etc/gitconfig
>> rather than from all available files.
>> @@ -214,7 +215,8 @@ $XDG_CONFIG_HOME/git/config::
>> file was added fairly recently.
>>
>> $(prefix)/etc/gitconfig::
>> - System-wide configuration file.
>> + System-wide configuration file, unless $(prefix) is /usr. In the
>> + latter case /etc/gitconfig is used.
>>
>> If no further options are given, all reading options will read all
>> of these
>> files that are available. If the global or the system-wide
>> configuration
>> --
>> 1.8.3.rc0.19.g7e6a0cc
>>
>>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
