From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] config: honor file permission bits
Date: Thu, 22 Oct 2026 16:29:18 -0700 [thread overview]
Message-ID: <xmqqa4o5co1d.fsf@gitster.g> (raw)
In-Reply-To: <atp7Pvtp1rdL8Uj_@fruit.crustytoothpaste.net> (brian m. carlson's message of "Thu, 22 Oct 2026 21:08:15 +0000")
"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.
next prev parent reply other threads:[~2026-10-22 23:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 14:27 [RFC/PATCH] config: honor file permission bits Junio C Hamano
2026-10-22 20:59 ` Junio C Hamano
2026-10-22 21:08 ` brian m. carlson
2026-10-22 23:29 ` Junio C Hamano [this message]
2026-10-23 8:23 ` Patrick Steinhardt
2026-10-23 14:54 ` Junio C Hamano
2026-10-26 8:40 ` Patrick Steinhardt
2026-10-26 15:01 ` Junio C Hamano
2026-10-26 14:59 ` [PATCH v2] " Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqa4o5co1d.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.