Re: Bug: git config does not respect read-only .gitconfig file

2016-11-09 Thread Jonathan Word
> It is unreasonable to drop the write-enable bit of > a file in a writable directory and expect it to stay unmodified. The > W-bit on the file is not usable as a security measure, and we do not > use it as such. The point here is not a matter of security - it is of expectations. When a user drop

Re: Bug: git config does not respect read-only .gitconfig file

2016-11-08 Thread Jonathan Word
ivar_in_file_gently which would only add respect for file-level permissions to the one command. Cheeers, On Tue, Nov 8, 2016 at 11:49 AM, Markus Hitter wrote: > Am 08.11.2016 um 16:22 schrieb Jonathan Word: >> Proposal: >> >> Part 1) Add a .gitconfig variable to resp

Bug: git config does not respect read-only .gitconfig file

2016-11-08 Thread Jonathan Word
All, I recently discovered that `git config` does not respect read-only files. This caused unexpected difficulty in managing the global .gitconfig for a system account shared by a large team. A team member was able to execute a `git config --global` command without any notice or warning that the