Conversation
Contributor
Author
Contributor
Author
Contributor
|
The change is fine with me. It all depends on how we expect the vagrant setup to be used. If it's just for checking things out, a minimal history is fine. However, if we want people to use it as a dev environment, we might want the full history. I think at this point the jdk download is the most time consuming task. |
Contributor
Author
|
do you need the full history to develop? I think you can still do a branch and work like normal, no? I'll test it real quick |
Contributor
|
If that's the case, then merge away.
|
Contributor
Author
jwomeara
added a commit
that referenced
this pull request
Apr 10, 2015
Reduce vagrant geowave clone depth
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.