public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Tian Yuchen <cat@malon.dev>
To: Dronaraj Gyawali <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: Tue, 10 Mar 2026 00:23:17 +0800	[thread overview]
Message-ID: <615caf83-71be-43a6-bcb0-3a0c5e14d699@malon.dev> (raw)
In-Reply-To: <CAJtK1FMzbX7dO9y7hM_6_DbLpwbeYHnrg7WLjAghGX6UDVDmJw@mail.gmail.com>

Hi drona,

Junio C Hamano <gitster@pobox.com> writes:

 > There were discussions on pros and cons moving global recipients of
 > configuration values into a dynamically allocated strucrure...
 > and excellent pieces of advice have been given by Phillip Wood.
 > If anything, a change like this should ask for input from him.

That makes sense. I think you should CC him whenever you've thoroughly 
polished the patch or when you encounter unresolved issues.

 > This "v2" applies to a mythical codebase where trust_executable_bit
 > is somehow a member in the settings structure, which I do not think
 > we have.

Given Junio's observation, it seems this iteration is targeting an 
incorrect or non-existent codebase structure.

I'll hold off on further reviews of the specific implementation details
until the base codebase issue is sorted out and the structural design
(incorporating Phillip's previous advice) is settled.

Looking forward to the updated version!

Thanks,

Yuchen

  reply	other threads:[~2026-03-09 16:23 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
2026-03-09 13:33       ` Dronaraj Gyawali
2026-03-09 16:23         ` Tian Yuchen [this message]
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=615caf83-71be-43a6-bcb0-3a0c5e14d699@malon.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox