-
Notifications
You must be signed in to change notification settings - Fork 2.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
rename libpod nettypes fields #12319
Conversation
Some field names are confusing. Change them so that they make more sense to the reader. Since these fields are only in the main branch we can safely rename them without worrying about backwards compatibility. Note we have to change the field names in netavark too. Signed-off-by: Paul Holzinger <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Some field names are confusing. Change them so that they make more sense to the reader. I also added copmment to the types to provide more context. also see containers/podman#12319 Signed-off-by: Paul Holzinger <[email protected]>
Some field names are confusing. Change them so that they make more sense to the reader. I also added comments to the types to provide more context. also see containers/podman#12319 Signed-off-by: Paul Holzinger <[email protected]>
netavark PR: containers/netavark#79 |
LGTM |
LGTM |
/lgtm |
What this PR does / why we need it:
Some field names are confusing. Change them so that they make more sense
to the reader.
Since these fields are only in the main branch we can safly rename them
without worrying about backwards compatibility.
Note we have to change the field names in netavark too.
How to verify it
Which issue(s) this PR fixes:
Special notes for your reviewer: