-
Notifications
You must be signed in to change notification settings - Fork 59
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
do we need sparse checkouts? #153
Comments
You should not use this feature. |
sparse checkouts are different from shallow clones. Sparse checkout allow to checkout a subdirectory. In the rust case it might make a big difference. Who wants to have 35M in ~/.vim if some kb would be enough? .. |
OK. I get it. |
thanks :) |
sparse checkouts are not smaller in size (.git) - but the size of checked out files could be less. In the rust case its 35 (all) vs 5MB (.git) 40K (vim directory). So it might still be worth it. |
Do you want to save disk usage instead of download size? |
You made a statement: "But sparse checkouts does not save your diskspace" and the example I gave proofs your statement wrong. In the rust case you get approx 5MB instead of 35MB disk usage. |
A lot of changes/fixes were made to sparse checkouts with git 1.9 So its possible both of you are right depending on what version you're using. |
Yes, it is my mistake. Sorry. |
Oh, my git version is 1.8.4.2(Ubuntu 13.10). |
VundleVim/Vundle.vim#252
sparse checkouts seem to allow checking out subdirectories of repositories.
The rust repository https://github.com/mozilla/rust referenced there is 35M in size (shallow clone depth=1)
This is related to runtime key
The text was updated successfully, but these errors were encountered: