-
Notifications
You must be signed in to change notification settings - Fork 38
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
make listening socket creation optional for userspace path manager plugins #297
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the PR! It looks good to me, but I think it will break the API, and it looks like we can avoid that easily, no?
Pull Request Test Coverage Report for Build 10286346027Details
💛 - Coveralls |
Modified the PR so that a new |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! It looks good to me, just two last small requests if that's OK for you.
@mjmartineau / @ossama-othman : because this modifies the public API, do you mind having a quick look please?
Modified the PR to avoid double negation check. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the update! It looks good to me, but I prefer to wait for Ossama or Mat's feedback (if they are available).
It looks like the issue with the CI is due to an API breakage on ELL side. I just opened a new bug report as it is not due to these modifications, anybody can fix it: #299 |
@ossama-othman: if you have the opportunity, do you mind having a quick look because this PR modifies the public API please? :) |
@matttbe Sure! I'll take a look today. @marco-a-itl Thank you very much for the PR! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good to me. Thank you very much!
Perhaps not in this PR, but when releasing a new version of mptcpd the NEWS
file could be updated with a description of the API addition, as well bumping the libtool versioning accordingly. From configure.ac
:
# ---------------------------------------------------------------
# Libtool Based Library Versioning
# ---------------------------------------------------------------
# Source changed: REVISION++
# Interfaces changed: CURRENT++ REVISION=0
# added: CURRENT++ REVISION=0 AGE++
# removed: CURRENT++ REVISION=0 AGE=0
LIB_CURRENT=3
LIB_REVISION=0
LIB_AGE=0
Thank you! Just squashed and merged!
OK, noted!
So here, because only new things have been added, I would need to update both |
The API has been modified: only new items have been added, see multipath-tcp#297 and It is then required to increase CURRENT and AGE, according to libtool's documentation. Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>
The API has been modified: only new items have been added, see PR multipath-tcp#297 and multipath-tcp#304. It is then required to increase CURRENT and AGE, according to libtool's documentation. Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>
The API has been modified: only new items have been added, see PR #297 and #304. It is then required to increase CURRENT and AGE, according to libtool's documentation. Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>
Proposal to resolve #296