From: Yuvraj Singh Chauhan <ysinghcin@gmail.com>
To: git@vger.kernel.org
Subject: [QUESTION] Improving disk space recovery for partial clones (GSoC 2026)
Date: Mon, 9 Mar 2026 17:43:59 +0530 [thread overview]
Message-ID: <aa65h6Z_TrpJbmkj@ThinkPad-E14-Gen-6> (raw)
Hi,
I'm interested in working on the "Improve disk space recovery for partial clones" project.
I am studying the codebase, particularly promisor-remote.c, builtin/backfill.c,
and the partial clone documentation.
I have a question to clarify the scope and direction of the project.
The project description mentions that git-backfill vs git-gc vs
git-repack vs git-maintenance is still undecided.
Has there been any recent discussion or consensus on this?
I want to make sure my proposal aligns with the community's direction.
sincerely,
Yuvraj
next reply other threads:[~2026-03-09 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 12:13 Yuvraj Singh Chauhan [this message]
2026-03-09 13:46 ` [QUESTION] Improving disk space recovery for partial clones (GSoC 2026) Christian Couder
2026-03-09 14:22 ` Yuvraj Singh Chauhan
2026-03-09 14:47 ` Christian Couder
2026-03-09 18:45 ` Yuvraj Singh Chauhan
2026-03-23 8:48 ` Yuvraj Singh Chauhan
2026-03-24 11:04 ` Christian Couder
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=aa65h6Z_TrpJbmkj@ThinkPad-E14-Gen-6 \
--to=ysinghcin@gmail.com \
--cc=git@vger.kernel.org \
/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