git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Editing GSoC Project Ideas

From
PWPhillip Wood <phillip.wood123@gmail.com>
Date
Mar 4, 2026, 15:56 UTC
Message-ID
<28ebbc8f-4b3c-4d2a-b9f4-046de95923ed@gmail.com>
In-Reply-To
<8bf53293-f2cb-4780-9ece-a77f32f485d7@gmail.com>
Hi Kaartic
On 02/03/2026 18:03, Kaartic Sivaraam wrote:
Show 27 quoted lines
> +Cc Stolee
> 
> Hi Phillip,
> 
> On 02/03/26 03:48, Christian Couder wrote:
>>
>> On Sun, Mar 1, 2026 at 3:26 PM Phillip Wood 
>> <phillip.wood123@gmail.com> wrote:
>>>
>>> I'd be very grateful if someone with write access could please update
>>> the description of "Refactoring in order to reduce Git’s global state"
>>> [1] to stop recommending moving settings from `environment.c` into
>>> `struct repository_settings`. That struct was originally added to hold
>>> config settings that were already lazily parsed. We've had a number of
>>> submissions that move eagerly parsed config settings into that struct
>>> where an invalid config setting causes git to start dying in unexpected
>>> places when the lazy parsing fails.
>>
>> Yes, we should definitely update the description. Thanks for telling
>> us about this.
>>
> 
> Indeed. Thank you for the suggestion. We've tried to tweak the 
> description accordingly. Kindly check and let us know if it still needs 
> any tweaks:
> 
>    https://git.github.io/SoC-2026-Ideas/
Thanks for updating that, it is certainly much clearer.
Show 14 quoted lines
>>> I haven't been following Stolee's work [3] on "git conifg list --type"
>>> closely but I think it introduces some functions to parse config
>>> settings gently. Those functions might enable us to parse some config
>>> settings lazy where the functions using the lazily parsed settings are
>>> already set up to return a error. Doing that would require careful
>>> analysis and should not be a blanket recommendation.
>>
>> I haven't followed Stolee's work either, but I will take a look.
>> Thanks for the pointer.
>>
> 
> I've not yet mentioned stolee's work in the tweak as it is a work in 
> progress. I'll leave it for a future enhancement in case it is really 
> worth mentioning the same.

That sounds sensible as none of us have actually thought through if it is useful yet.

Show 7 quoted lines
>> In the meantime, if you have concrete suggestions for change you can
>> submit one or more PRs to the https://github.com/git/git.github.io/
>> repo.
>>
> 
> Just to add to this, any patches via mailing-list are also welcome if 
> that's preferred :-)
Thanks I'll bear that in mind
Phillip
Previous: Kaartic Sivaraam
Message 4 of 4 in “Editing GSoC Project Ideas”
  1. Phillip WoodMar 1, 2026
  2. Christian CouderMar 1, 2026
  3. Kaartic SivaraamMar 2, 2026
  4. Phillip WoodMar 4, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.