Jeff King wrote: > For example, servers may depend on /etc/gitconfig to enforce security > policy (e.g., setting transfer.fsckObjects or receive.deny*). Perhaps > our default should be safe, and people can use GIT_CONFIG_NOSYSTEM to > work around a broken machine.
Very good point. How about these patches on top? Jonathan Nieder (2): config doc: advertise GIT_CONFIG_NOSYSTEM config: exit on error accessing any config file Documentation/git-config.txt | 8 ++++++++ config.c | 6 +++--- 2 files changed, 11 insertions(+), 3 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
