-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide vdrift-data on github.com or other git hoster #146
Comments
Yeah, this has been discussed a number of times. If it was just a few hundred MBs, it would have happened already. We are talking about ~3.5GB binary data though. See also https://help.github.com/articles/what-is-my-disk-quota/ So the motivation from my side is not very high. ;) |
@krichter722 Hosting vdrift-data on GitHub was discussed in https://github.com/Bengt/VDrift-Data/issues/2, for example. I basically dumped a SVN checkout into a Git repository to evaluate that idea. Although this worked in principle, there were some issues that could not be resolved completely. However, Git now has way better support for large binary files, making a Git-based workflow much more viable. |
I imported VDrift using GitHub's importer: https://github.com/Bengt/VDrift-2016-07-09 VDrift is actually that small (1.81 GB) in Git that it can reside in a single repository. Given today's broadband internet connections and cheap SSDs, splitting the repository up into multiple submodules does not seem worth the hassle and neither does using (and paying for) LFS. I suspect that enabling collaboration via pull requests is more important than being able to work with individual assets, nowadays. |
I've tried to checkout the latest vdrift-data using subversion from sourceforge, but it failed like:
|
Entering the svn checkout directoring and issuing A better command to avoid checking out extraneous directories:
|
It'd be nice to have
vdrift-data
from https://sourceforge.net/p/vdrift/code/HEAD/tree/ at github.com or asgit
some other way.The text was updated successfully, but these errors were encountered: