From: Phillip Wood <phillip.wood123@gmail.com>
To: Tian Yuchen <a3205153416@gmail.com>, 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>
Subject: Re: [GSoC][Draft Proposal v4] Refactoring in order to reduce Git's global state
Date: Fri, 27 Feb 2026 09:03:46 +0000 [thread overview]
Message-ID: <1d43d1d0-bf6b-4806-834e-89f545fab766@gmail.com> (raw)
In-Reply-To: <5e5f07ec-72ba-46ee-812c-d6773a4bdbe7@gmail.com>
Hi Tian
On 26/02/2026 17:02, Tian Yuchen wrote:
> [...]
> Although the principle is simple, the scope of changes is extensive. The
> following three-step approach can serve as a guiding principle for it:
There are four steps below
> 1. Identify isolated environment variables currently residing in the
> global scope. Conduct a case-by-case analysis to map each variable
> to its most appropriate existing home (e.g., struct repo_settings
> for configuration values, or specific localized structs within
> struct repository).
Note that as settings in struct repo_settings are lazily parsed, it is
only suitable for settings that are already lazily parsed. That means it
is not a suitable home for any settings that are parsed at startup by
git_default_config().
> 2. Instead of blindly passing struct repository *repo down into every
> single low-level library function, bubbling the dependency up is
> the true goal. External callers of the functions must be carefully
> audited to prevent regressions.
Where a function only needs one piece of information from struct
repository that sounds like a good strategy.
> 3. Safely remove the old global variables and macro definitions. Make
> full use of Git's existing GitLab/GitHub CI and utilize local
> Meson builds with AddressSanitizer enabled to ensure that the new
> lifecycle introduces zero memory leaks.
> 4. Many globals like `editor_program` are parsed once and remain
> available globally. New data flow might need to be designed to
> maintain the lazy-loading efficiency.
Although `editor_program` is parsed once, that happens in
git_default_config() so it is not lazily loaded and making it lazily
loaded would be a regression as if the config value is invalid we want
to exit with an error early in the process, not just before we prompt
the user to edit a file.
Thanks
Phillip
next prev parent reply other threads:[~2026-02-27 9:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 17:59 [GSoC][Draft Proposal] Refactoring in order to reduce Git's global state Tian Yuchen
2026-02-22 18:34 ` Usman Akinyemi
2026-02-23 0:57 ` Tian Yuchen
2026-02-23 1:07 ` [GSoC][Draft Proposal V2] " Tian Yuchen
2026-02-25 17:11 ` [GSoC][Draft Proposal v3] " Tian Yuchen
2026-02-26 9:27 ` Karthik Nayak
2026-02-26 14:03 ` Tian Yuchen
2026-02-26 14:16 ` Tian Yuchen
2026-02-26 17:02 ` [GSoC][Draft Proposal v4] " Tian Yuchen
2026-02-27 9:03 ` Phillip Wood [this message]
2026-02-27 15:07 ` Tian Yuchen
2026-02-27 16:58 ` Tian Yuchen
2026-03-01 16:43 ` Phillip Wood
2026-03-01 16:58 ` Tian Yuchen
2026-03-02 19:06 ` Junio C Hamano
2026-03-03 12:11 ` [GSoC][Draft Proposal v6] " Tian Yuchen
2026-03-08 17:38 ` [GSoC][Draft Proposal v7] " Tian Yuchen
2026-03-14 17:57 ` Tian Yuchen
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=1d43d1d0-bf6b-4806-834e-89f545fab766@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=a3205153416@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=phillip.wood@dunelm.org.uk \
--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