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:19 UTC
Message-ID
<nycvar.QRO.7.76.6.1707232119210.20418@qynat-yncgbc>
In-Reply-To
<CANENsPpdQzBqStGjq4jUsAB0-7U8_SQq+=kjmJe6pJtiXxnYFg@mail.gmail.com>
On Mon, 24 Jul 2017, Farshid Zavareh wrote:
Show 5 quoted lines
> I see your point. So I guess it really comes down to how the file is
> anticipated to change. If only one or two line are going to change every
> now and then, then LFS is not really necessary. But, as you mentioned, text
> files that change drastically will affect the repository in the same way
> that binaries do.

Not quite the same way that binaries do, because text files compress well. but close.

David Lang
Previous: Farshid ZavarehNext: Andrew Ardill
Message 6 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.