This is an automated email from the ASF dual-hosted git repository.
weizhouapache pushed a change to branch docker-image-build
in repository https://gitbox.apache.org/repos/asf/cloudstack.git
discard c77429f6931 remove duplicated NODE_OPTIONS
discard 8ef45794a5b docker: add MAVEN_OPTS
discard cf739192334 docker: run UI with NODE_OPTIONS=--openssl-legacy-provider
discard 56a233babf5 tools: Build docker image
add d2a3bd1aa78 Rename draft-THREAT-MODEL.md to THREAT_MODEL.md (#13599)
add 13742921d1e Fix simulator test failures on main (#13608)
add 332800480df debian/ubuntu: ignore pycompile errors (#13602)
add e550521ac15 tools: Build docker image
add 753931d80cb docker: run UI with NODE_OPTIONS=--openssl-legacy-provider
add d42692346c1 docker: add MAVEN_OPTS
add 4697a815569 remove duplicated NODE_OPTIONS
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 (c77429f6931)
\
N -- N -- N refs/heads/docker-image-build (4697a815569)
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:
SECURITY.md | 2 +-
draft-THREAT-MODEL.md => THREAT_MODEL.md | 0
debian/cloudstack-common.postinst | 12 ++++++------
.../com/cloud/configuration/ConfigurationManagerImpl.java | 2 --
test/integration/component/test_vpc_offerings.py | 6 +++---
5 files changed, 10 insertions(+), 12 deletions(-)
rename draft-THREAT-MODEL.md => THREAT_MODEL.md (100%)
