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

Re: [QUESTION] Improving disk space recovery for partial clones (GSoC 2026)

From
Yuvraj Singh Chauhan <ysinghcin@gmail.com>
Date
Mar 23, 2026, 08:48 UTC
Message-ID
<acD-esOCTH3PpK9y@ThinkPad-E14-Gen-6>
In-Reply-To
<aa8VWlv7dosrrRwv@ThinkPad-E14-Gen-6>
On Tue, Mar 10, 2026 at 12:15:46AM +0530, Yuvraj Singh Chauhan wrote:
Show 9 quoted lines
> I have been studying the different commands and how they work, I will put together
> my understanding in a pros and cons list for each command and send it asap.
> 
> Also the contributor application period starts March 16 and ends on the March 31.
> Can I complete my proposal for community review in between that period as well? or
> should I rush to write a draft version before that.
> 
> sincerely,
> Yuvraj
After some studying here the four options for placement:
Option A: git backfill --evict
Remark: 'backfill' semantically means to fill in what is missing. Adding removal semantics creates confusion. Project idea has also signalled backfill is unlikely to be the right location. The traversal logic for eviction differs enough from backfill's that there wont be a well structured shared code.
Option B: git gc / git repack
Remark: gc is already complex and runs automatically. Stolee's concern, that background tools like VS Code running git blame will immediately re-download evicted blobs, which argues directly against automatic eviction. A user who runs git gc -a does not expect silent network activity.
Option C: git maintenance task
Remark: maintenance can be a long-term home for scheduled eviction, but only after the core eviction logic is stable. An idle-detection heuristic (not yet designed) would be needed before automatic eviction is safe.
Option D: git evict (standalone command)
Remark: User-driven invocation is the approach that safely addresses Stolee's re-download concern. When the user explicitly runs git evict, they have context about what they are about to lose. No background tool can trigger git evict accidentally. This placement also avoids semantic confusion and creates a clean audit surface for the community to review.
Please review so that I can create the proposed plan accordingly

sincerely, Yuvraj Singh Chauhan

Previous: Yuvraj Singh ChauhanNext: Christian Couder
Message 6 of 7 in “[QUESTION] Improving disk space recovery for partial clones (GSoC 2026)”
  1. Yuvraj Singh ChauhanMar 9, 2026
  2. Christian CouderMar 9, 2026
  3. Yuvraj Singh ChauhanMar 9, 2026
  4. Christian CouderMar 9, 2026
  5. Yuvraj Singh ChauhanMar 9, 2026
  6. Yuvraj Singh ChauhanMar 23, 2026
  7. Christian CouderMar 24, 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.