git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Francesco Paparatto <francescopaparatto@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org, Ayush Chandekar <ayu.chandekar@gmail.com>,
	jltobler@gmail.com,
	 Siddharth Asthana <siddharthasthana31@gmail.com>,
	karthik nayak <karthik.188@gmail.com>
Subject: Re: [GSoC Proposal] Refactoring in order to reduce Git's global state
Date: Sat, 21 Mar 2026 14:56:46 +0100	[thread overview]
Message-ID: <CAEaT9__zLj+9YQCn-nWqRL6qF=T4rUnY2r6Un=1cjZEFOP8dmw@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD1H8ZsxfGSnnvX9xkKLSSpDjA3e3KNZ7eHN3ruq-sC7fw@mail.gmail.com>

Christian Couder <christian.couder@gmail.com> writes:

Hi Christian,
Thanks for the feedback.

>
> For commits which graduated to master, please give the commit ID of
> either the commits you authored or the merge commit that merged your
> commit(s) into master.

I will add the commit IDs in v2.

>
> By the way there is also this series from Olamide Bello:
>
> https://lore.kernel.org/git/cover.1773127785.git.belkid98@gmail.com/

Thanks for pointing me to Olamide's latest series, I will
study it and use it to map the remaining repo_config_values
work directly in the proposal.

Best,
Francesco


  reply	other threads:[~2026-03-21 13:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 17:54 [GSoC Proposal] Refactoring in order to reduce Git's global state Francesco Paparatto
2026-03-21 13:36 ` Christian Couder
2026-03-21 13:56   ` Francesco Paparatto [this message]
2026-03-21 16:32   ` Junio C Hamano
2026-03-24 19:31 ` [GSoC Proposal v2] " Francesco Paparatto
  -- strict thread matches above, loose matches on Subject: below --
2026-03-06 14:57 [GSOC][PROPOSAL]: Refactoring in order to reduce Git’s " Shreyansh Paliwal
2026-03-07 10:33 ` Christian Couder
2026-03-07 12:46   ` Shreyansh Paliwal

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEaT9__zLj+9YQCn-nWqRL6qF=T4rUnY2r6Un=1cjZEFOP8dmw@mail.gmail.com' \
    --to=francescopaparatto@gmail.com \
    --cc=ayu.chandekar@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jltobler@gmail.com \
    --cc=karthik.188@gmail.com \
    --cc=siddharthasthana31@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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).