-
Notifications
You must be signed in to change notification settings - Fork 168
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
Don't use shallow clones #81
Comments
I implemented shallow clone after read above thread. |
The problem persists for example with ack.vim plugin. The error message says:
Quick test that fails:
But this one succeeds:
The problem persists in about 10% of repositories, what makes dealing with such repos unreliable. Note: I've send this issue to Github, but don't count on quick fix. Moreover there is no quick and reliable way to convert shallow repo to full one, so I can make changes. Shallow repo always will be shallow, even when all commits are fetched with --depth=1000000 for example. |
OK. I disabled shallow clones. |
Time heavily depends on amount of history. History can be fetched by git fetch --depth=99999 easily later. |
VAM has been using shallow clones for a long time - no issues were reported. |
Yes, you are lucky. But it is not solved the problem. |
I cannot reproduce the problem in git 2.6.2... |
I've got similar issues to this one: Homebrew/legacy-homebrew@8a1c2ec
Please, disable shallow cloning, the download time doesn't take much longer.
The text was updated successfully, but these errors were encountered: