19 ms·
You should not be checking in binary files into git. That defeats the entire purpose and bloats the repo size enormously. Git LFS should be used instead. Or st
by munmaek 7y ago
You should not be checking in binary files into git. That defeats the entire purpose and bloats the repo size enormously.
Git LFS should be used instead. Or storing a Sha256sum and putting the file elsewhere.
- imtringued 7y agoThat is a solution but then it's no longer distributed.
- alkonaut 7y agoBeing distributive isn’t a feature for the binary files contents. I don’t want 100 historical versions of a huge game texture, just the latest one. The history is distributed however, so I can see who changed the texture even when disconnected. Centralized binaries like git LFS works like any package/asset manager. There is no one that would want distributed binaries in git. But people also don’t want to switch from git to something else just because they have a 100GB or 10TB repo. Tooling (build tools, issue management) everywhere has decided that git is all that’s needed. Not putting binaries in git isn’t a solution at all. Binaries are part of the source in many applications (e.g game assets, web site images...). Distributing every version of every binary to everyone is also not a solution.