Re: [RFC/PATCH] config: honor file permission bits
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 22, 2026, 23:29 UTC
- Message-ID
- <xmqqa4o5co1d.fsf@gitster.g>
- In-Reply-To
- <atp7Pvtp1rdL8Uj_@fruit.crustytoothpaste.net>
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> I don't personally make that file read-only, so it doesn't affect me at > all; instead, I just overwrite it with my personal configuration every > time I deploy my dotfiles.
> I don't personally make that file read-only, so it doesn't affect me at > all; instead, I just overwrite it with my personal configuration every > time I deploy my dotfiles.
Well, I deploy my dotfiles from the freshly built one (the sources of dotfiles are kept elsewhere under version control), too, but when "installing", I make them read-only, just like all other "installed" files like the contents of my ~/bin/ directory. My personal makefiles have "dry-run" support to tell me what the changes are in the version I am about to install in 'patch' form, and that is how I noticed that "git config" allowed to make such a mistake, even though the file is read-only, to some failed experiment I made earlier.