This is an automated email from the ASF dual-hosted git repository.

rohit pushed a change to branch debian9-systemvmtemplate
in repository https://gitbox.apache.org/repos/asf/cloudstack.git.


 discard 6837ca5  CLOUDSTACK-10127: KVM + Ovs: Incorrect devId on static nat
 discard 128c999  CLOUDSTACK-10001: Fix incorrect total host memory in responses
 discard 2c0b4eb  CLOUDSTACK-10013: Add systemvm 4.11 migration in 4.10->4.11 
upgrade path
 discard 89e079b  CLOUDSTACK-10194: Use packer for building systemvmtemplates
     new 5650ff2  CLOUDSTACK-10194: Use packer for building systemvmtemplates
     new 0c320fe  CLOUDSTACK-10013: Add systemvm 4.11 migration in 4.10->4.11 
upgrade path
     new 1c65ac4  CLOUDSTACK-10001: Fix incorrect total host memory in responses
     new b91e885  CLOUDSTACK-10127: KVM + Ovs: Incorrect devId on static nat

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   (6837ca5)
            \
             N -- N -- N   refs/heads/debian9-systemvmtemplate (b91e885)

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.

The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 engine/schema/src/com/cloud/upgrade/dao/Upgrade41000to41100.java      | 4 ++++
 tools/appliance/systemvmtemplate/scripts/install_systemvm_packages.sh | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

-- 
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].

Reply via email to