#Git large file storage full

However, as long as you still have your exact binary files sitting around somewhere, you can always import them back on the fly, so e.g. Whereas with git-annex, it is true that without rewriting history, even if you disable git-annex moving forward, you'll still have symlinks in your git history. There is now always a source of truth that is inconvenient to work around when you might still have the files lying around on a bunch of different hard drives or USB drives.

#Git large file storage full

In particular it's pretty annoying to have to always spin up a full HTTPS server just to be able to have access to your files. The 'one-way door' as I understand the article to be describing is talking about the additional layer of centralization that Git LFS brings. If you want to completely disable use of largefiles then you still have to run `hg lfconvert` at some point. In particular, AFAICT, Mercurial requires the exact same thing as what you're pointing out. The way that the author talks about Mercurial as not having this problem makes me think they're talking about something related but subtly different.