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

Use newly-created 'common' repo #2061

Merged
merged 5 commits into from
Dec 7, 2016
Merged

Use newly-created 'common' repo #2061

merged 5 commits into from
Dec 7, 2016

Conversation

jml
Copy link
Contributor

@jml jml commented Dec 6, 2016

Fixes #2509

This means we can re-use this code in other weave repos without having to depend on scope.

Copy link
Contributor

@paulbellamy paulbellamy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's with +20k lines of new vendored stuff?

@jml
Copy link
Contributor Author

jml commented Dec 6, 2016

I don't know.

@jml
Copy link
Contributor Author

jml commented Dec 6, 2016

Running gvt restore on scope produces huge numbers of changes. Maybe I'm doing it wrong?

@jml
Copy link
Contributor Author

jml commented Dec 6, 2016

I've made a totally new PR (#2062) that does gvt restore on master. gvt fetch github.com/weaveworks/common still brings in new vendoring. I don't know why, and I don't know why it should prevent this PR from being merged.

PTAL.

@jml jml mentioned this pull request Dec 7, 2016
@tomwilkie
Copy link
Contributor

Extra vendoring can be explained by weaveworks/common including tools, which has a bunch of go stuff, which you've pulled in the libraries for. Its not a big deal.

@jml
Copy link
Contributor Author

jml commented Dec 7, 2016

#2066 talks a bit about that.

@jml jml merged commit 9a92961 into master Dec 7, 2016
@jml jml deleted the use-common-lib branch December 7, 2016 11:51
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