From: Ayush Jha <kumarayushjha123@gmail.com>
To: git@vger.kernel.org
Cc: Christian Couder <christian.couder@gmail.com>,
Karthik Nayak <karthik.188@gmail.com>,
Justin Tobler <jltobler@gmail.com>,
Ayush Chandekar <ayu.chandekar@gmail.com>,
Siddharth Asthana <siddharthasthana31@gmail.com>,
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>,
Ayush Jha <kumarayushjha123@gmail.com>
Subject: [RFC GSoC PATCH v3 0/2] Make read_attr() repository-aware by introducing a lazy bare state
Date: Sun, 8 Feb 2026 11:59:47 +0530 [thread overview]
Message-ID: <20260208062949.596-1-kumarayushjha123@gmail.com> (raw)
This patch series is v3 of an earlier RFC that aimed to remove the
dependency on the global `the_repository` from read_attr().
Based on feedback from Lucas Seiki Oshiro and Junio C Hamano, this
iteration introduces a repository-scoped, lazily initialized "bare"
state in struct repo_settings, exposed via repo_settings_get_is_bare().
The read_attr() function is then updated to use this helper instead of
is_bare_repository().
The series is split as follows:
1/2 repo-settings: add repo_settings_get_is_bare
2/2 attr: use local repository state in read_attr
Comments and suggestions are welcome.
Ayush Jha (2):
repo-settings: add repo_settings_get_is_bare
attr: use local repository state in read_attr
attr.c | 3 ++-
repo-settings.c | 12 ++++++++++++
repo-settings.h | 5 +++++
3 files changed, 19 insertions(+), 1 deletion(-)
--
2.53.0.windows.1
next reply other threads:[~2026-02-08 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 6:29 Ayush Jha [this message]
2026-02-19 9:42 ` [RFC GSoC PATCH v3 0/2] Make read_attr() repository-aware by introducing a lazy bare state Ayush Jha
2026-02-19 10:42 ` Phillip Wood
2026-02-19 15:01 ` Ayush Jha
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=20260208062949.596-1-kumarayushjha123@gmail.com \
--to=kumarayushjha123@gmail.com \
--cc=ayu.chandekar@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jltobler@gmail.com \
--cc=karthik.188@gmail.com \
--cc=lucasseikioshiro@gmail.com \
--cc=siddharthasthana31@gmail.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