public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Christian Couder <christian.couder@gmail.com>,
	phillip.wood@dunelm.org.uk
Cc: Patrick Steinhardt <ps@pks.im>,
	Karthik Nayak <karthik.188@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Derrick Stolee <stolee@gmail.com>
Subject: Re: Editing GSoC Project Ideas
Date: Mon, 2 Mar 2026 23:33:13 +0530	[thread overview]
Message-ID: <8bf53293-f2cb-4780-9ece-a77f32f485d7@gmail.com> (raw)
In-Reply-To: <CAP8UFD2Q7gctwzGOe+rbgdXZSbDbV0dmM-cx4qt_d8nKi88=HA@mail.gmail.com>

+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/

>> 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.

> 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 :-)

--
Sivaraam


  reply	other threads:[~2026-03-02 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01 14:26 Editing GSoC Project Ideas Phillip Wood
2026-03-01 22:18 ` Christian Couder
2026-03-02 18:03   ` Kaartic Sivaraam [this message]
2026-03-04 15:56     ` Phillip Wood

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=8bf53293-f2cb-4780-9ece-a77f32f485d7@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=karthik.188@gmail.com \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=ps@pks.im \
    --cc=stolee@gmail.com \
    /path/to/YOUR_REPLY

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

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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