Comment by jayd16
1 day ago
It does seem like this proposal has exactly the same issue. Unless this new method blocks cloning when unable to access the promisors, you'll end up with similar problems of broken large files.
1 day ago
It does seem like this proposal has exactly the same issue. Unless this new method blocks cloning when unable to access the promisors, you'll end up with similar problems of broken large files.
How so? This proposal doesn’t require you to run `git lfs install` to get the correct files…
If the architecture is irrelevant and it's just a matter of turning it on by default they could have done that with LFS long ago.
Git lfs can't do it by default because:
1. It is a separate tool that has to be installed separately from git
2. It works by using git filters and git hooks, which need to be set up locally.
Something built in to git doesn't have those problems.
1 reply →
And what happens when an object is missing from the cloud storage or that storage has been migrated multiple times and someone turns down the old storage that’s needed for archival versions?
You obviously get errors in that case, which is not great.
But GP's point was that there is an entire other category of errors with git-lfs that are eliminated with this more native approach. Git-lfs allows you to get into an inconsistent state e.g. when you interrupt a git action that just doesn't happen with native git.
1 reply →