summaryrefslogtreecommitdiff
path: root/t/t5515/fetch.br-config-glob-octopus
diff options
context:
space:
mode:
authorLibravatar Jonathan Nieder <jrnieder@gmail.com>2012-10-13 17:04:02 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-10-13 21:59:16 -0700
commit96b9e0e313604f77456906ce58db8f366e47f2ab (patch)
tree67632a6ba4f7918ae40b58519dfa3ea3f794af4f /t/t5515/fetch.br-config-glob-octopus
parentconfig, gitignore: failure to access with ENOTDIR is ok (diff)
downloadtgif-96b9e0e313604f77456906ce58db8f366e47f2ab.tar.xz
config: treat user and xdg config permission problems as errors
Git reads multiple configuration files: settings come first from the system config file (typically /etc/gitconfig), then the xdg config file (typically ~/.config/git/config), then the user's dotfile (~/.gitconfig), then the repository configuration (.git/config). Git has always used access(2) to decide whether to use each file; as an unfortunate side effect, that means that if one of these files is unreadable (e.g., EPERM or EIO), git skips it. So if I use ~/.gitconfig to override some settings but make a mistake and give it the wrong permissions then I am subject to the settings the sysadmin chose for /etc/gitconfig. Better to error out and ask the user to correct the problem. This only affects the user and xdg config files, since the user presumably has enough access to fix their permissions. If the system config file is unreadable, the best we can do is to warn about it so the user knows to notify someone and get on with work in the meantime. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/fetch.br-config-glob-octopus')
0 files changed, 0 insertions, 0 deletions