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

Why Git LFS is not a built-in feature

From
AAlireza <rezaxm@gmail.com>
Date
Nov 13, 2020, 09:45 UTC
Message-ID
<CAD9n_qjKyxNjtd1YrcHzshLg0-vbwXkHRwMveXHAWSOXMWLKAg@mail.gmail.com>

Currently, having to set up git-lfs in each client and checking server compatibility is a huge barrier for using it in the first place, whilst it is generally a good practice to store large files in lfs.

As a consequence a lot of repos are not using it when they should.

Is there any reason that we don't have built-in support for such an important feature?

Next: brian m. carlson
Message 1 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.