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

Re: GIT and large files

From
Junio C Hamano <gitster@pobox.com>
Date
May 20, 2014, 17:18 UTC
Message-ID
<xmqqmwec1i9f.fsf@gitster.dls.corp.google.com>
In-Reply-To
<C755E6FBF6DC4447BEF161CE48BDE0BD2F0CD53E@XMBVAG73.northgrum.com>
"Stewart, Louis (IS)" <louis.stewart@ngc.com> writes:
> Can GIT handle versioning of large 20+ GB files in a directory?

I think you can "git add" such files, push/fetch histories that contains such files over the wire, and "git checkout" such files, but naturally reading, processing and writing 20+GB would take some time. In order to run operations that need to see the changes, e.g. "git log -p", a real content-level merge, etc., you would also need sufficient memory because we do things in-core.

Previous: Marius Storm-OlsenNext: Stewart, Louis (IS)
Message 4 of 10 in “GIT and large files”
  1. Stewart, Louis (IS)May 20, 2014
  2. Jason PyeronMay 20, 2014
  3. Marius Storm-OlsenMay 20, 2014
  4. Junio C HamanoMay 20, 2014
  5. Stewart, Louis (IS)May 20, 2014
  6. Junio C HamanoMay 20, 2014
  7. Stewart, Louis (IS)May 20, 2014
  8. Konstantin KhomoutovMay 20, 2014
  9. Thomas BraunMay 20, 2014
  10. Stewart, Louis (IS)May 20, 2014

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.