4 ms·

Re-cloning a fresh repo should keep it small. There's also a git gc method which cleans up the repo. I guess another way would be to just archive all the histor

• masklinn 12y ago
  > Re-cloning a fresh repo should keep it small. There's also a git gc method which cleans up the repo. There's only so much git gc can do. We've got a 500MB repo (.git, excluding working copy) at work, for 100k revisions. That's with a fresh clone and having tried most combinations of gc and repack we could think of. Considering the size of facebook, I can only expect that their repo is deeper (longer history in revisions count), broader (more files), more complex and probably full of binary stuff.
  • Dylan16807 12y ago
    Is that all actually code? Each commit would have to add an average of 5KB compressed so maybe 20KB of brand new code.
    • masklinn 12y ago
      > Is that all actually code? Of course not, it's an actual project. There is code, there are data files (text and binary) and there are assets.