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

Splitting off old history to ancillary repo

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Aug 28, 2008, 02:40 UTC
Message-ID
<46a038f90808271940w3aaf5c4ek6329e8066724c778@mail.gmail.com>

A project I've inherited has a codebase ~500KB in size. However, in early history some large binary blobs were committed to the repo. We've gotten rid of those, and they are not interesting to current development. But an initial checkout still has to retrieve 60MiB, when I'm sure the recent (and interesting) history fits in less than 1MB.

What is the state of grafts from a "keeping the repo mostly transparently usable for newcomers" POV? Is there a new mechanims I should look at?

Do we have a documented "here's how you split your repo with minimal downsides to end users"? If you give me enough hints I could write it :-)

The repo in question is http://dev.laptop.org/git?p=projects/xs-config;a=summary
cheers,
m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
Next: Michael J Gruber
Message 1 of 2 in “Splitting off old history to ancillary repo”
  1. Martin LanghoffAug 28, 2008
  2. Michael J GruberAug 28, 2008

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.