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

Partial Clone garbage collection?

From
SHSimon Holmberg <simon.holmberg@avalanchestudios.se>
Date
Oct 30, 2019, 17:08 UTC
Message-ID
<CA+M_GG1SfxGW=p_=418hdR1ypB3v-4GrooK6_75UUNJDb+kk2Q@mail.gmail.com>
In-Reply-To
<CA+M_GG35V3yNCfQ247PSrpP-R_f8bWNcBcmrnTWbrn1Nap_A4A@mail.gmail.com>

I've been experimenting with the new Partial Clone feature, attempting to use it to filter out the otherwise full history of the large binary resources in our repos. It works really well on the initial clone. But once you start jumping around in history a lot, the repo will grow out of proportion again as promised pack files are fetched.

Are there any plans to add a --filter parameter to git gc as well, that would be able to prune past history of objects and convert them back into pack promises? Or am I wrong in assuming that this could ever act as a native replacement for LFS? Without this, a repo would only continue to grow ad infinitum, resulting in the same issues as before unless you actively chose to delete your entire clone and re-clone it from upstream once in a while.

Next: без имени
Message 1 of 5 in “Partial Clone garbage collection?”
  1. Simon HolmbergOct 30, 2019
  2. без имениOct 30, 2019
  3. Jeff KingOct 30, 2019
  4. Jeff KingOct 30, 2019
  5. Jonathan TanOct 30, 2019

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.