Skip to content

Reduce vagrant geowave clone depth#324

Merged
jwomeara merged 1 commit intomasterfrom
GEOWAVE-323
Apr 10, 2015
Merged

Reduce vagrant geowave clone depth#324
jwomeara merged 1 commit intomasterfrom
GEOWAVE-323

Conversation

@chrisbennight
Copy link
Copy Markdown
Contributor

No description provided.

@chrisbennight
Copy link
Copy Markdown
Contributor Author

#323

@chrisbennight
Copy link
Copy Markdown
Contributor Author

@jwomeara

@jwomeara
Copy link
Copy Markdown
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.

@chrisbennight
Copy link
Copy Markdown
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

@jwomeara
Copy link
Copy Markdown
Contributor

If that's the case, then merge away.
On Apr 9, 2015 9:57 PM, "Chris Bennight" notifications@github.com wrote:

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


Reply to this email directly or view it on GitHub
#324 (comment).

@chrisbennight
Copy link
Copy Markdown
Contributor Author

jwomeara added a commit that referenced this pull request Apr 10, 2015
Reduce vagrant geowave clone depth
@jwomeara jwomeara merged commit 076fcaa into master Apr 10, 2015
@jwomeara jwomeara deleted the GEOWAVE-323 branch April 10, 2015 03:12
@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 32.86% when pulling f876e2e on GEOWAVE-323 into 4b814ec on master.

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

Successfully merging this pull request may close these issues.

3 participants