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

[GSoC] Introduction

From
Francesco Paparatto <francescopaparatto@gmail.com>
Date
Feb 27, 2026, 18:35 UTC
Message-ID
<CAEaT9_8nL6v0i4Ge=aG8o5abZXTbJ8EwF4ekUfho0MLU6zi0_w@mail.gmail.com>
Hi everyone,

I'm Francesco from Italy, and I'm interested in contributing to Git as part of GSoC 2026. I've confirmed that I meet all GSoC eligibility requirements.

I've been studying how Git works under the hood by reimplementing some core plumbing commands in C, which got me interested in the project.

So far, I've built Git from source, read the "CodingGuidelines", "SubmittingPatches", "MyFirstContribution" and the "General Microproject Information" page. I've also enabled CI on my GitHub fork.

For my microproject, I chose to replace old-style test -f and test -d checks with test_path_is_file and test_path_is_dir in t3310-notes-merge-manual-resolve.sh. I found the instances using git grep "test -[efd]" t/ and searched the mailing list archives to make sure t3310 wasn't already taken and to look at past attempts at this type of conversion. I'll send my patch in a separate thread.

Beyond the microproject, I'm interested in the "Move global state into the repository object" project.

Looking forward to feedback.

Thanks, Francesco

Message 1 of 1 in “[GSoC] Introduction”
  1. Francesco PaparattoFeb 27, 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.