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

Re: Why Git LFS is not a built-in feature

From
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Date
Nov 14, 2020, 16:27 UTC
Message-ID
<20201114162700.cvmxzcs4sdhsxpak@chatter.i7.local>
In-Reply-To
<20201114002902.GN6252@camp.crustytoothpaste.net>
On Sat, Nov 14, 2020 at 12:29:02AM +0000, brian m. carlson wrote:
Show 6 quoted lines
> Additionally, in many cases, projects can avoid the need for storing
> large files at all by using repository best practices, like not storing
> build products or binary dependencies in the repository and instead
> using an artifact server or a standard packaging system.  If possible,
> that will almost always provide a better experience than any solution
> for storing large files in the repository.

Well, I would argue that if the goal is ongoing archival and easy replication, then storing objects in a repository like git makes a lot more sense than keeping them on a central server that may or may not be there a few years down the line. Having large file support native in git is a laudable goal and I quite often wish that it existed.

-K
Previous: brian m. carlsonNext: Ævar Arnfjörð Bjarmason
Message 3 of 6 in “Why Git LFS is not a built-in feature”
  1. AlirezaNov 13, 2020
  2. brian m. carlsonNov 14, 2020
  3. Konstantin RyabitsevNov 14, 2020
  4. Ævar Arnfjörð BjarmasonNov 14, 2020
  5. Partial clone demo for large files (Re: Why Git LFS is not a built-in feature)Christian Couder, Nov 18, 2020
  6. brian m. carlsonNov 14, 2020

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.