-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Move weaveworks/common back to upstream #945
Comments
As weaveworks/common#153 is more or less dead and waiting for a rebase I reopened a new (rebased) PR (weaveworks/common#167). |
Hello! Can I work on this after weaveworks/common#167 is merged? |
@clickyotomy If you are more familiar with the dependencies a bit of help in weaveworks/common#167 would be most welcome. Initially it was only meant to be a rebase to resolve a merge conflict, but now the actual change has been reviewed again. |
@clickyotomy Please also take a look at my notes in #1051 as there is apparently another version in the |
@ThoreKr, I am not familiar with the changes introduced in weaveworks/common#167, but I will try to help. :)
How do I make changes to the PR? Fork from https://github.com/ThoreKr/weaveworks-common/tree/server-listen-addr and open a new one? Regarding #1051, this repo was moved to |
@clickyotomy Me neither, I just rebased it. Maybe wait for comments from upstream whether it should be tested or not. |
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Still waiting for weaveworks-common. Starting to get annoyed. |
@clickyotomy it's merged! |
To not block some PR we moved weaveworks/common to a personal fork. Once weaveworks/common#153 is merged we can go back to upstream.
The text was updated successfully, but these errors were encountered: