This is an automated email from the ASF dual-hosted git repository. Pearl1594 pushed a change to branch minor-improvements-clvm in repository https://gitbox.apache.org/repos/asf/cloudstack.git
discard ec97c3138de CLVM: Cleanup and improvements discard c68af0374a4 Merge branch 'main' of https://github.com/apache/cloudstack discard fac45d6e335 Merge branch 'main' of https://github.com/apache/cloudstack omit fd59bf641fa Merge branch 'main' of https://github.com/apache/cloudstack omit 95e81e15bcf Merge branch 'main' of https://github.com/apache/cloudstack omit 343ea4054ed Merge branch 'main' of https://github.com/apache/cloudstack omit c087de4adfe Merge branch '4.19' new a7b9a414fa1 CLVM: Fix volume mapping and disk path matching for storage migration 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 (ec97c3138de) \ N -- N -- N refs/heads/minor-improvements-clvm (a7b9a414fa1) 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 1 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:
