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

GIT as binary repository

From
WEWilson, Kevin Lee (OpenView Engineer) <kevin.l.wilson@hp.com>
Date
Oct 21, 2010, 12:52 UTC
Message-ID
<2EBB46ACFCD6CF48B45E2B1865BD02338037D36B4E@GVW1098EXB.americas.hpqcorp.net>
Hello, 
We are investigating the use of GIT as a binary repository solution. Our larger files are near 800MB and the total checked out repo size is about 3 GB the repo size in SVN is more like 20-30GB, if we could prune the history prior to MR, we could get these sizes down considerably. This binary repo is really for our super project build.  From what I have read and learned, this is not a good fit for the GIT tool. Have there been performance improvements lately? Some of the posts I have read have been quite old?
I also have some questions, about how the workflow would be for getting all of the changes merged from several different teams into the one repository would operate. Do we setup a shared system for engineers to perform the merges onto? Our teams are geographically disbursed. 
Thanks for any light you can shed on this. We are trying to digest a lot of information quickly, so sorry if there are things covered here that are elsewhere.

Thanks, Kevin

Next: Tay Ray Chuan
Message 1 of 9 in “GIT as binary repository”
  1. Wilson, Kevin Lee (OpenView Engineer)Oct 21, 2010
  2. Tay Ray ChuanOct 21, 2010
  3. Enrico WeigeltOct 21, 2010
  4. Shawn PearceOct 21, 2010
  5. Enrico WeigeltOct 22, 2010
  6. Shawn PearceOct 22, 2010
  7. Shawn PearceOct 21, 2010
  8. Wilson, Kevin Lee (OpenView Engineer)Oct 21, 2010
  9. Enrico WeigeltOct 21, 2010

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.