-
Notifications
You must be signed in to change notification settings - Fork 3
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
use shallow clone for analysis #38
Comments
Thank you for the suggestion. I'm not completely sure what you mean, though. Which context are we talking about, the |
I was aiming for the |
I did a few experiments.
The improvements 1. and 2. can be implemented easily but will typically not gain us a lot. 3.1 is relatively effective (300 MB instead of more than 1 GB for opencv) but doesn't work for all cases: directly specified commits as well unusual ref names will not be present in the cache entry. 3.2 is very effective and also correct but complicated so implementing it may not be worth the trouble. |
Regarding 3.2: Don't you know the required refs anyway? You could even fetch individual refs on demand only, i.e. only fetch the ones that you actually need for the present analysis. Usually, within a distribution, we don't often switch between different versions, do we? |
Is it possible to use
git clone --depth n
to just clone the recent history of the requested branch?Some repos, e.g. OpenCV, have a huge history and take ages to download fully.
The text was updated successfully, but these errors were encountered: