Git development
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] config: honor file permission bits
Date: Thu, 5 Nov 2026 14:27:24 +0100	[thread overview]
Message-ID: <auyEPBEDUziv4w8u@pks.im> (raw)
In-Reply-To: <xmqqld797msp.fsf@gitster.g>

On Tue, Nov 03, 2026 at 11:11:18AM -0800, Junio C Hamano wrote:
> 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?

Maybe? I guess. In any case, no user has ever asked about this, so it's
probably okay. Not that any user has asked about the proposed new
behaviour either, as far as I know.

> >> +		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 ;-).

I don't think the other messages would need to be adapted. We already
have a mixture of both styles in this files, so I'd prefer to at least
not make the status quo worse by adding more instances that we know to
be suboptimal.

In any case, these are just nits and I don't feel strongly about any of
them.

Patrick

  reply	other threads:[~2026-11-05 13:27 UTC|newest]

Thread overview: 13+ 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
2026-11-05 13:27       ` Patrick Steinhardt [this message]
2026-11-05 18:12         ` 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=auyEPBEDUziv4w8u@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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