From: Yuvraj Singh Chauhan <ysinghcin@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [QUESTION] Improving disk space recovery for partial clones (GSoC 2026)
Date: Mon, 9 Mar 2026 19:52:10 +0530 [thread overview]
Message-ID: <aa7XkqhcG6Kb6IhN@ThinkPad-E14-Gen-6> (raw)
In-Reply-To: <CAP8UFD3sicsPd903FU8bsj2B_4Q1DE1xB+--OxryY_jhL=sHdw@mail.gmail.com>
On Mon, Mar 09, 2026 at 02:46:06PM +0100, Christian Couder wrote:
> Hi Yuvraj,
>
> On Mon, Mar 9, 2026 at 1:14 PM Yuvraj Singh Chauhan <ysinghcin@gmail.com> wrote:
> >
> > 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.
>
> Thanks for your interest in Git and this project.
>
> > 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.
>
> I don't think that there is a consensus on this. It seems to me that
> someone said that git-backfill was likely not the best command for
> this, but I don't remember where and when this happened. It could have
> been in a private discussion.
>
> Best.
So should I understand the all the different ways and create a document for the command
I think would be a good fit and why. And then the community can give their opinion on it?
sincerely,
Yuvraj
next prev parent reply other threads:[~2026-03-09 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 12:13 [QUESTION] Improving disk space recovery for partial clones (GSoC 2026) Yuvraj Singh Chauhan
2026-03-09 13:46 ` Christian Couder
2026-03-09 14:22 ` Yuvraj Singh Chauhan [this message]
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=aa7XkqhcG6Kb6IhN@ThinkPad-E14-Gen-6 \
--to=ysinghcin@gmail.com \
--cc=christian.couder@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