{"thread":{"id":"65006","subject":"[GSoC 2026 Inquiry] Refactoring global state","startedAt":"2026-02-17T07:57:35Z","lastAt":"2026-02-17T15:55:21Z","messageCount":3,"participants":["Tian Yuchen","Karthik Nayak"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"536149","messageId":"7a95b0f4-8242-4418-bc54-22e81cf40019@gmail.com","threadId":"65006","inReplyTo":null,"subject":"[GSoC 2026 Inquiry] Refactoring global state","fromName":"Tian Yuchen","fromEmail":"a3205153416@gmail.com","sentAt":"2026-02-17T07:57:31Z","receivedAt":"2026-02-17T07:57:35Z","isPatch":false,"sender":{"key":"cat@malon.dev","avatar":"https://avatars.githubusercontent.com/u/232002048?v=4"},"body":"Hi Christian, Karthik, Justin.. and Git community,\n\nMy name is Tian Yuchen. I am an undergraduate year 1 student who's new \nto the Git community. I've been hanging around the community for over a \nmonth now, contributing almost every day. I really love the vibe here!\n\nI'm quite interested in applying for the GSoC project \"Refactoring in \norder to reduce Git's global state\":\n\nCoincidentally, just as the new idea list for this year was released \nthese past few days, I've been working on a patch that has some \nconnections to this project. (setup.c: handling named pipes/FIFOs during \ngit directory discovery, currently in v4). Indeed, based on my \nexperience, this requires tremendous patience, but I'm more than willing \nto give it a try.\n\nI understand that removing global state is a massive, multi-year effort. \nI assume the goal of the GSoC project is not to finish everything, but \nto pick a specific area or a set of related modules and migrate them to \nuse 'struct repository' explicitly.\n\nMy Question:\n\nDo you have a specific module or subsystem in mind that you would like \nto prioritize for this summer?\n\nFor example, would focusing on 'environment.c' (as mentioned in the idea \nlist) be the primary target, or are there other areas (like 'config.c' \nor 'setup.c') that are currently blocking other major features?\n\nI would love to align my proposal with the community's current \npriorities. Thanks for your time!\n\nRegards,\n\nYuchen\n"},{"id":"536176","messageId":"CAOLa=ZQr_+fx1-j_dEbWJS=2BDUaFZ7ky6M-rLkBAWLVyd_d5g@mail.gmail.com","threadId":"65006","inReplyTo":"7a95b0f4-8242-4418-bc54-22e81cf40019@gmail.com","subject":"Re: [GSoC 2026 Inquiry] Refactoring global state","fromName":"Karthik Nayak","fromEmail":"karthik.188@gmail.com","sentAt":"2026-02-17T12:16:36Z","receivedAt":"2026-02-17T12:16:38Z","isPatch":false,"sender":{"key":"karthik.188@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1786334?v=4"},"body":"Tian Yuchen <a3205153416@gmail.com> writes:\n\n> Hi Christian, Karthik, Justin.. and Git community,\n>\n> My name is Tian Yuchen. I am an undergraduate year 1 student who's new\n> to the Git community. I've been hanging around the community for over a\n> month now, contributing almost every day. I really love the vibe here!\n>\n\nHello Tian,\n\n> I'm quite interested in applying for the GSoC project \"Refactoring in\n> order to reduce Git's global state\":\n\nHappy to hear that.\n\n>\n> Coincidentally, just as the new idea list for this year was released\n> these past few days, I've been working on a patch that has some\n> connections to this project. (setup.c: handling named pipes/FIFOs during\n> git directory discovery, currently in v4). Indeed, based on my\n> experience, this requires tremendous patience, but I'm more than willing\n> to give it a try.\n>\n> I understand that removing global state is a massive, multi-year effort.\n> I assume the goal of the GSoC project is not to finish everything, but\n> to pick a specific area or a set of related modules and migrate them to\n> use 'struct repository' explicitly.\n\nYup, that's correct, this was also a project a contributor worked on,\nlast year.\n\n>\n> My Question:\n>\n> Do you have a specific module or subsystem in mind that you would like\n> to prioritize for this summer?\n>\n> For example, would focusing on 'environment.c' (as mentioned in the idea\n> list) be the primary target, or are there other areas (like 'config.c'\n> or 'setup.c') that are currently blocking other major features?\n>\n\nAFAIK We don't have any specific subsystem to focus, albeit some\nsubsystems are tightly coupled and hence can be more complex (e.g.\n'setup.c'). So my advice would be to find a good balance, you could also\ntake tips from the patches submitted from the previous year.\n\n> I would love to align my proposal with the community's current\n> priorities. Thanks for your time!\n>\n\nThanks for checking in, perhaps others on the list have more to say.\n\n> Regards,\n>\n> Yuchen\n\nKarthik\n"},{"id":"536196","messageId":"6e038336-6b2d-4415-8710-7dae720fd4da@gmail.com","threadId":"65006","inReplyTo":"CAOLa=ZQr_+fx1-j_dEbWJS=2BDUaFZ7ky6M-rLkBAWLVyd_d5g@mail.gmail.com","subject":"Re: [GSoC 2026 Inquiry] Refactoring global state","fromName":"Tian Yuchen","fromEmail":"a3205153416@gmail.com","sentAt":"2026-02-17T15:55:17Z","receivedAt":"2026-02-17T15:55:21Z","isPatch":false,"sender":{"key":"cat@malon.dev","avatar":"https://avatars.githubusercontent.com/u/232002048?v=4"},"body":"Hi karthik,\n\nThanks for the swift reply and encouraging words!\n\n> AFAIK We don't have any specific subsystem to focus, albeit some\n> subsystems are tightly coupled and hence can be more complex (e.g.\n> 'setup.c'). So my advice would be to find a good balance, you could also\n> take tips from the patches submitted from the previous year.\n\nPoint taken. My recent experience with the 'setup.c' patch definitely \ntaught me to respect the complexity of that subsystem. I agree that \nmaking it the primary target for the entire summer might be too risky.\n\nI will follow your advice to dig into archives and log to study how \nprevious contributors structured their changes.\n\nThank you again for the feedback!\n\nRegards,\n\nYuchen\n\n\n"}]}