This is an automated email from the ASF dual-hosted git repository.
vishesh92 pushed a change to branch feat-add-stickyness-policy
in repository
https://gitbox.apache.org/repos/asf/cloudstack-kubernetes-provider.git
omit d4e61cec Feat: Add support for stickyness policy
add 7d27f2f7 Disable draft and push reviews in .asf.yaml (#108)
add 83b07d4f Feat: Add support for stickyness policy
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d4e61cec)
\
N -- N -- N refs/heads/feat-add-stickyness-policy (83b07d4f)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.asf.yaml | 4 ++--
cloudstack_loadbalancer.go | 33 ++++++++++++++++-----------------
cloudstack_loadbalancer_test.go | 30 ++++++++++++++++++++----------
3 files changed, 38 insertions(+), 29 deletions(-)
