public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Tian Yuchen <a3205153416@gmail•com>
To: Karthik Nayak <karthik.188@gmail•com>,
	Christian Couder <christian.couder@gmail•com>,
	Justin Tobler <jltobler@gmail•com>,
	Ayush Chandekar <ayu.chandekar@gmail•com>,
	Siddharth Asthana <siddharthasthana31@gmail•com>,
	Lucas Seiki Oshiro <lucasseikioshiro@gmail•com>
Cc: git@vger•kernel.org
Subject: [GSoC 2026 Inquiry] Refactoring global state
Date: Tue, 17 Feb 2026 15:57:31 +0800	[thread overview]
Message-ID: <7a95b0f4-8242-4418-bc54-22e81cf40019@gmail.com> (raw)

Hi Christian, Karthik, Justin.. and Git community,

My name is Tian Yuchen. I am an undergraduate year 1 student who's new 
to the Git community. I've been hanging around the community for over a 
month now, contributing almost every day. I really love the vibe here!

I'm quite interested in applying for the GSoC project "Refactoring in 
order to reduce Git's global state":

Coincidentally, just as the new idea list for this year was released 
these past few days, I've been working on a patch that has some 
connections to this project. (setup.c: handling named pipes/FIFOs during 
git directory discovery, currently in v4). Indeed, based on my 
experience, this requires tremendous patience, but I'm more than willing 
to give it a try.

I understand that removing global state is a massive, multi-year effort. 
I assume the goal of the GSoC project is not to finish everything, but 
to pick a specific area or a set of related modules and migrate them to 
use 'struct repository' explicitly.

My Question:

Do you have a specific module or subsystem in mind that you would like 
to prioritize for this summer?

For example, would focusing on 'environment.c' (as mentioned in the idea 
list) be the primary target, or are there other areas (like 'config.c' 
or 'setup.c') that are currently blocking other major features?

I would love to align my proposal with the community's current 
priorities. Thanks for your time!

Regards,

Yuchen

next             reply	other threads:[~2026-02-17  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17  7:57 Tian Yuchen [this message]
2026-02-17 12:16 ` [GSoC 2026 Inquiry] Refactoring global state Karthik Nayak
2026-02-17 15:55   ` 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=7a95b0f4-8242-4418-bc54-22e81cf40019@gmail.com \
    --to=a3205153416@gmail$(echo .)com \
    --cc=ayu.chandekar@gmail$(echo .)com \
    --cc=christian.couder@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jltobler@gmail$(echo .)com \
    --cc=karthik.188@gmail$(echo .)com \
    --cc=lucasseikioshiro@gmail$(echo .)com \
    --cc=siddharthasthana31@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox