Skip to content
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

Closed
sheerun opened this issue Apr 25, 2013 · 7 comments
Closed

Don't use shallow clones #81

sheerun opened this issue Apr 25, 2013 · 7 comments

Comments

@sheerun
Copy link

sheerun commented Apr 25, 2013

I've got similar issues to this one: Homebrew/legacy-homebrew@8a1c2ec

Please, disable shallow cloning, the download time doesn't take much longer.

@Shougo
Copy link
Owner

Shougo commented Apr 25, 2013

dimitri/el-get#915

I implemented shallow clone after read above thread.
Please describe the problem to me.

@sheerun
Copy link
Author

sheerun commented Apr 29, 2013

The problem persists for example with ack.vim plugin. The error message says:

fatal: git fetch-pack: expected shallow list  

Quick test that fails:

git clone https://github.com/mileszs/ack.vim --depth=1 && 
  cd ack.vim && 
  git fetch --depth=10 && git fetch --depth=10

But this one succeeds:

git clone https://github.com/mileszs/apidock.vim.git --depth=1 && 
  cd apidock.vim && 
  git fetch --depth=10 && git fetch --depth=10

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.

@Shougo
Copy link
Owner

Shougo commented Apr 30, 2013

OK. I disabled shallow clones.

@MarcWeber
Copy link

Time heavily depends on amount of history. History can be fetched by git fetch --depth=99999 easily later.

@MarcWeber
Copy link

VAM has been using shallow clones for a long time - no issues were reported.

@Shougo
Copy link
Owner

Shougo commented Feb 13, 2014

Yes, you are lucky. But it is not solved the problem.
You should search "expected shallow list" error message in search engines.

@Shougo
Copy link
Owner

Shougo commented Nov 14, 2015

I cannot reproduce the problem in git 2.6.2...
It is resolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants