Re: [PATCH] [RFC][GSoC][PATCH] attr: use local repository state in read_attr

From: Ayush Jha <kumarayushjha123@gmail.com>
Date: Feb 10, 2026, 14:05 UTC
Message-ID: <CAFNBzOckR2yfGvLMHm0VZW+iKJTgFxzfxQAskdBV2HQ_3yXggA@mail.gmail.com>
In-Reply-To: <96329bc6-0490-454b-a21b-babb85c98bc9@gmail.com>

Hello everyone,

I’ve incorporated the feedback provided on this patch and sent an updated version as a follow-up patch series:

[RFC GSoC PATCH v3 0/2] Make read_attr() repository-aware by introducing a lazy bare state [RFC GSoC PATCH v3 1/2] repo-settings: add repo_settings_get_is_bare [RFC GSoC PATCH v3 2/2] attr: use local repository state in read_attr

Since I’m still new to the Git community and the mailing-list workflow, I wanted to check whether I might have missed anything in the process (such as CCs, subject tags, or proper threading), as I haven’t received feedback on the updated patches yet.

Please let me know if there’s anything I should fix or do differently. I’d really appreciate any guidance.

Thank you for your time and for the earlier feedback.

Best regards, Ayush Jha

On Sun, Feb 8, 2026 at 10:12 AM Tian Yuchen <a3205153416@gmail.com> wrote:

Show 15 quoted lines

>
> Junio C Hamano <gitster@pobox.com> writes:
>
>  >The codepath read_attr() is in is usually not that hot but it is not
>  >cheap.
>
> I'm a bit curious—under what circumstances would calling this method
> result in significant performance regression?
>
> Regards,
>
> Yuchen
>
>
>