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

Shallow clone by default (#122 #217) #221

Merged
merged 3 commits into from
Apr 30, 2015
Merged

Shallow clone by default (#122 #217) #221

merged 3 commits into from
Apr 30, 2015

Conversation

junegunn
Copy link
Owner

No description provided.

@junegunn
Copy link
Owner Author

--unshallow should be used only once. 😲

@junegunn
Copy link
Owner Author

And fetch --unshallow requires git 1.8.2 or above.

@junegunn
Copy link
Owner Author

And git fetch --depth 99999999 is slower than git fetch.

@junegunn
Copy link
Owner Author

So here's the summary of this PR:

  1. Shallow clone (--depth 1)
    1. if g:plug_shallow is not set to 0 and tag is not specified.
    2. --no-single-branch option is also used for branch option
  2. PlugUpdate will git fetch --depth 99999999 when tag option is given to "unshallow" the repository
    1. Not --unshallow because it requires git 1.8.2 or above
    2. --depth 99999999 is attached only when the repository is indeed shallow (.git/shallow exists) because depth makes fetch noticeably slower.

junegunn added a commit that referenced this pull request Apr 30, 2015
@junegunn junegunn merged commit d738da2 into master Apr 30, 2015
@junegunn junegunn deleted the shallow-clone branch April 30, 2015 05:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant