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: Re: [GSoC 2026 Inquiry] Refactoring global state
Date: Tue, 17 Feb 2026 23:55:17 +0800	[thread overview]
Message-ID: <6e038336-6b2d-4415-8710-7dae720fd4da@gmail.com> (raw)
In-Reply-To: <CAOLa=ZQr_+fx1-j_dEbWJS=2BDUaFZ7ky6M-rLkBAWLVyd_d5g@mail.gmail.com>

Hi karthik,

Thanks for the swift reply and encouraging words!

> AFAIK We don't have any specific subsystem to focus, albeit some
> subsystems are tightly coupled and hence can be more complex (e.g.
> 'setup.c'). So my advice would be to find a good balance, you could also
> take tips from the patches submitted from the previous year.

Point taken. My recent experience with the 'setup.c' patch definitely 
taught me to respect the complexity of that subsystem. I agree that 
making it the primary target for the entire summer might be too risky.

I will follow your advice to dig into archives and log to study how 
previous contributors structured their changes.

Thank you again for the feedback!

Regards,

Yuchen



      reply	other threads:[~2026-02-17 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17  7:57 [GSoC 2026 Inquiry] Refactoring global state Tian Yuchen
2026-02-17 12:16 ` Karthik Nayak
2026-02-17 15:55   ` Tian Yuchen [this message]

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=6e038336-6b2d-4415-8710-7dae720fd4da@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
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