git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Date
Feb 14, 2026, 00:04 UTC
Message-ID
<03F6CE03-751E-43D5-80E2-E799D97B09B2@gmail.com>
In-Reply-To
<CAFNBzOckR2yfGvLMHm0VZW+iKJTgFxzfxQAskdBV2HQ_3yXggA@mail.gmail.com>
> Hello everyone,
Hello again, Ayush!
Show 7 quoted lines
> 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
Two tips about working with our mailing lists:
1. Normally here we sent next versions replying to the cover letter
   of the first version. You can use the flag --in-reply-to in
   git-send-email(1) to do that. (This is a Git thing, some other
   patch-based FLOSS projects don't do that).
2. When we reference other messages, we use the message id instead of
   the subject. For example, I'm referencing your message [1] in this
   sentence.
> Best regards,
> Ayush Jha
Thanks and welcome!
[1] CAFNBzOckR2yfGvLMHm0VZW+iKJTgFxzfxQAskdBV2HQ_3yXggA@mail.gmail.com/
Previous: Ayush JhaNext: Ayush Jha
Message 7 of 10 in “attr: use local repository state in read_attr”
  1. [RFC][GSoC][PATCH] attr: use local repository state in read_attrAyush Jha, Feb 7, 2026
  2. Tian YuchenFeb 7, 2026
  3. Lucas Seiki OshiroFeb 7, 2026
  4. Junio C HamanoFeb 7, 2026
  5. Tian YuchenFeb 8, 2026
  6. Ayush JhaFeb 10, 2026
  7. Lucas Seiki OshiroFeb 14, 2026
  8. Ayush JhaFeb 14, 2026
  9. Junio C HamanoFeb 10, 2026
  10. Tian YuchenFeb 11, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.