optional git-lfs #1171
Merged
optional git-lfs #1171
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Byron
force-pushed
the
lfs-independence
branch
4 times, most recently
from
2b4d04d to
762cc39
Compare
… where possible Maybe this also means that one should prefer to not use git-lfs at all and keep data in the packs themselves, it still shouldn't be too much overall. Butl... for now, let's try to keep it to make the experience. Here we choose the quick way out by simply checking in the archives in question and by disabling git-lfs for them. That way, most of the scripts still run, but we don't have to square the circle trying to get these scripts portable, or spend a lot of time figuring out why some baselines don't match perfectly (on windows).
Byron
force-pushed
the
lfs-independence
branch
from
762cc39 to
b6f2b81
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Maybe this also means that one should prefer to not use git-lfs at all
and keep data in the packs themselves, it still shouldn't be too much overall.
Butl... for now, let's try to keep it to make the experience.