git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Francesco Paparatto <francescopaparatto@gmail.com>
To: git@vger.kernel.org
Cc: christian.couder@gmail.com, karthik nayak <karthik.188@gmail.com>,
	jltobler@gmail.com,  Ayush Chandekar <ayu.chandekar@gmail.com>,
	Siddharth Asthana <siddharthasthana31@gmail.com>
Subject: [GSoC] Introduction
Date: Fri, 27 Feb 2026 19:35:25 +0100	[thread overview]
Message-ID: <CAEaT9_8nL6v0i4Ge=aG8o5abZXTbJ8EwF4ekUfho0MLU6zi0_w@mail.gmail.com> (raw)

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


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

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 18:35 Francesco Paparatto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-10  2:40 [GSoC] Introduction Lorenzo Pegorari
2026-01-10 16:33 ` Christian Couder
2026-01-01  8:08 Pushkar Singh
2026-01-05 10:01 ` Christian Couder
2025-12-30 16:12 [GSOC] Introduction Kavyansh Bagdi
2026-01-05 10:38 ` Christian Couder
2025-12-24  2:14 [GSoC] Introduction Andrew Chitester
2025-12-27 10:07 ` Christian Couder
2020-01-22 20:42 Shourya Shukla
2020-01-23 11:02 ` Christian Couder
2020-01-23 18:04   ` Shourya Shukla
2020-01-23 22:51     ` Christian Couder
2020-01-01 13:02 [GSOC] Introduction Hariom verma
2020-01-23 11:16 ` Christian Couder
2020-01-23 20:18   ` Hariom verma
2020-01-23 22:38     ` Christian Couder
2019-02-24 10:05 [GSoC] Introduction Rohit Ashiwal
2019-02-24 14:47 ` Johannes Schindelin
2019-02-25  6:50 ` Christian Couder
2019-02-25 11:35   ` Rohit Ashiwal
2019-02-25 20:21     ` Christian Couder
2019-02-25 21:09       ` Eric Sunshine
2015-03-07 11:25 [GSOC] Introduction karthik nayak

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_8nL6v0i4Ge=aG8o5abZXTbJ8EwF4ekUfho0MLU6zi0_w@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).