list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Alireza <>
Subject: Why Git LFS is not a built-in feature
Date: Fri, 13 Nov 2020 13:15:52 +0330	[thread overview]
Message-ID: <> (raw)

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?

             reply	other threads:[~2020-11-13  9:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13  9:45 Alireza [this message]
2020-11-14  0:29 ` Why Git LFS is not a built-in feature brian m. carlson
2020-11-14 16:27   ` Konstantin Ryabitsev
2020-11-14 18:20     ` Ævar Arnfjörð Bjarmason
2020-11-18 10:20       ` Partial clone demo for large files (Re: Why Git LFS is not a built-in feature) Christian Couder
2020-11-14 19:15     ` Why Git LFS is not a built-in feature brian m. carlson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).