From: Tian Yuchen <a3205153416@gmail•com>
To: phillip.wood@dunelm•org.uk, 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: Mon, 2 Mar 2026 00:58:17 +0800 [thread overview]
Message-ID: <7fa1f5c9-d1c1-4d81-a170-74a77468b923@gmail.com> (raw)
In-Reply-To: <eecd6531-a7b5-4f0e-8e4d-3807f47d1f9d@gmail.com>
Hi Phillip,
Thank you so much for taking the time to review both my patch and my
GSoC proposal draft.
You are right on all points:
1. I now agree that commit encoding being a user/environment preference
rather than a repository-specific attribution. My example was indeed a
flawed assumption.
2. Thank you for catching the contradiction between my patch and my
proposal's guiding principles. However, I changed it to lazy-loading not
because I didn't follow the workflow I wrote, but because I thought the
original eagerly parsing behavior was *incorrect*. But since I now
understand point 1 above, this is no longer an issue to me anymore.
3. I deeply appreciate you pointing out that the GSoC ideas page might
be misleading. I will study through the link you provide.
Thank you again for steering me in the right direction!
Regards,
Yuchen
next prev parent reply other threads:[~2026-03-01 16:58 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
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 [this message]
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=7fa1f5c9-d1c1-4d81-a170-74a77468b923@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=phillip.wood@dunelm$(echo .)org.uk \
--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