On Jul 10, 2020, at 8:52 AM, Alin Serdean <[email protected]>
wrote:
>
> Most of these changes should not change user-visible behavior. One
> place where they do is in "ovs-ofctl dump-flows", which will now output
> "subs:..." inside "bundle" actions instead of "slaves:...". I don't
> expect this to cause real problems in most systems. The old syntax
> is still supported on input for backward compatibility.
>
> Signed-off-by: Ben Pfaff <[email protected]>
> ---
> As discussed offline instead of the term “sub-interface” maybe use “member”.
>
> Leaving the link for the MSFT naming convention:
> https://docs.microsoft.com/en-us/powershell/module/netlbfo/add-netlbfoteammember?view=win10-ps
I see that there is still some discussion ongoing regarding these four
inclusive-language patches.
What's the probability that these patches will be included in the upcoming
v2.14 release?
I ask for two reasons:
1. There was a prior email about July 17th being the branch date for v2.14.
I'm not sure what this means in terms of a planned final release date.
2. I have an ongoing patch ("AB bonding: Add "primary" interface concept")
about AB bonding that will almost certainly cause conflicts with these patches.
I'm happy to adjust/rebase my patch on top of these patches, but would need
the final patches to do so (especially if the AB bonding patch is to make it
into v2.14).
Alternatively, is it possible that my AB bonding patch would be committed
before these inclusive-language patches?
I guess I'm trying to say: if either of these patches are to be committed in
the near future, the other will likely need to adjust for conflicts.
--
Jeff Squyres
[email protected]
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
