All of lore.kernel.org
 help / color / mirror / Atom feed
From: cat@malon.dev
To: drona <dronarajgyawali@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Git <git@vger.kernel.org>
Subject: Re: [PATCH v2] Make 'trust_executable_bit' repository-scoped
Date: Mon, 09 Mar 2026 15:13:34 +0800	[thread overview]
Message-ID: <6e3d373f2f41232ca9015c39ae0ea67d@purelymail.com> (raw)
In-Reply-To: <f03d40072ab106d1a0a7852718d42f56@purelymail.com>

> Hi drona,
> 
> Thanks for the update! Just a quick heads-up: it looks like
> you forgot to CC Junio (gitster@pobox.com) on this iteration.
> Additionally, I think it's a good practice to respond to
> reviews before sending new patches. What do you think?
> 
>>  	if (!strcmp(var, "core.filemode")) {
>> +		prepare_repo_settings(the_repository);
>>  		the_repository->settings.trust_executable_bit = 
>> git_config_bool(var, value);
>>  		return 0;
>>  	}
> 
> Regarding the code, calling 'prepare_repo_settings()' inside
> 'git_default_core_config()' defeats the purpose of lazy-loading,
> doesn't it?
> 
> if (!strcmp(var, "core.filemode")) {
> 	prepare_repo_settings(the_repository);
> 	the_repository->settings.trust_executable_bit = git_config_bool(var, 
> value);
> 	return 0;
> }
> 
> I think the standard practice is to drop the variable from
> 'environment.c' completely and read it directly inside
> 'repo-settings.c: prepare_repo_settings()' using
> 'repo_config_get_bool()'.
> 
> Regards,
> 
> Yuchen

I accidentally clicked the wrong option and didn't select Reply All.

I'll CC Junio on this message.

Regards,

Yuchen

  parent reply	other threads:[~2026-03-09  7:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01 18:59 [PATCH] Refactor 'trust_executable_bit' to repository-scoped setting drona
2026-03-06 18:02 ` Tian Yuchen
2026-03-08 18:24 ` [PATCH] Make 'trust_executable_bit' repository-scoped drona
2026-03-08 18:34 ` [PATCH] [PATCH v2] " drona
2026-03-08 18:37 ` drona
     [not found]   ` <f03d40072ab106d1a0a7852718d42f56@purelymail.com>
2026-03-09  7:13     ` cat [this message]
2026-03-09 13:33       ` Dronaraj Gyawali
2026-03-09 16:23         ` Tian Yuchen
2026-03-09 22:03           ` Junio C Hamano
2026-03-09 15:07       ` Junio C Hamano
2026-03-09 17:51         ` Dronaraj Gyawali

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=6e3d373f2f41232ca9015c39ae0ea67d@purelymail.com \
    --to=cat@malon.dev \
    --cc=dronarajgyawali@gmail.com \
    --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 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.