Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] config: honor file permission bits
Date: Tue, 03 Nov 2026 11:11:18 -0800	[thread overview]
Message-ID: <xmqqld797msp.fsf@gitster.g> (raw)
In-Reply-To: <aum4pZp5P0ZRC-cf@pks.im> (Patrick Steinhardt's message of "Tue, 3 Nov 2026 11:34:13 +0100")

Patrick Steinhardt <ps@pks.im> writes:

> Nit: a curious reader might wonder why such in-tree files don't need
> such protection.

But isn't it self evident that repository contents are supposed to
be mutable, and you are not even supposed to muck with filesystem
level tools like chmod or mv to begin with?

>> +		error_errno(_("file %s unwritable"), config_filename);
>
> Should we quote '%s' here? The function is quite inconsistent, where it
> sometimes quotes and sometimes doesn't. I'd say that quoting is the
> better choice though.

While it probably makes sense, many of the existing messages in the
same function also lack the quote.  I would rather leave it for
others to clean up the subsystem as a whole, as I expect there would
probably be a huge fallout in expected test output ;-).

      reply	other threads:[~2026-11-03 19:11 UTC|newest]

Thread overview: 11+ 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
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
2026-11-03 10:34   ` Patrick Steinhardt
2026-11-03 19:11     ` Junio C Hamano [this message]

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=xmqqld797msp.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox