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

Re: Should I store large text files on Git LFS?

From
DLDavid Lang <david@lang.hm>
Date
Jul 24, 2017, 04:13 UTC
Message-ID
<nycvar.QRO.7.76.6.1707232109480.20418@qynat-yncgbc>
In-Reply-To
<FF08CB42-35AC-4B97-BB02-2473BEDE66A1@gmail.com>
On Mon, 24 Jul 2017, Farshid Zavareh wrote:
Show 5 quoted lines
> I'll probably test this myself, but would modifying and committing a 4GB text 
> file actually add 4GB to the repository's size? I anticipate that it won't, 
> since Git keeps track of the changes only, instead of storing a copy of the 
> whole file (whereas this is not the case with binary files, hence the need for 
> LFS).

well, it wouldn't be 4G because text compresses well, but if the file changes drastically from version to version (say a quarterly report), the diff won't help.

David Lang
Previous: Farshid ZavarehNext: Farshid Zavareh
Message 4 of 14 in “Should I store large text files on Git LFS?”
  1. Farshid ZavarehJul 24, 2017
  2. Andrew ArdillJul 24, 2017
  3. Farshid ZavarehJul 24, 2017
  4. David LangJul 24, 2017
  5. Farshid ZavarehJul 24, 2017
  6. David LangJul 24, 2017
  7. Andrew ArdillJul 24, 2017
  8. Jeff KingJul 24, 2017
  9. Junio C HamanoJul 24, 2017
  10. Andrew ArdillJul 25, 2017
  11. Jeff KingJul 25, 2017
  12. Junio C HamanoJul 25, 2017
  13. Jeff KingJul 25, 2017
  14. Stefan BellerJul 25, 2017

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.