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

git subtree as a solution to partial cloning?

From
AAAsger Ottar Alstrup <asger@area9.dk>
Date
May 25, 2009, 07:35 UTC
Message-ID
<8873ae500905250035h74fc366ct907998c62e518fcf@mail.gmail.com>

I am considering different ways to get git to handle repositories with very big files in a setup where partial clone is required, and it seems git subtree might be a part of the solution.

Does git subtree support splitting at the file level, or only at directory level? Also, how are conflicts handled when you subtree merge changes back to the master? For this to work in practice, I suppose the users of the split repositories should see the conflicts and fix them themselves. Can the reduced split repositories reuse pack files from the original repository? Can you think of any other limitations to git subtree that would prevent it from working with big files to support a partial cloning setup?

The alternative seems to be git sparse checkout extended with non-existing narrow clone, but it seems that a git subtree based approach might be simpler.

Regards, Asger Ottar Alstrup

Message 1 of 1 in “git subtree as a solution to partial cloning?”
  1. Asger Ottar AlstrupMay 25, 2009

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.