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

dahn pushed a change to branch staging-site
in repository https://gitbox.apache.org/repos/asf/cloudstack-www.git


 discard b0b3d4da captial to lower case p
     add b5a9d000 ff-only
     add a522d907 Merge remote-tracking branch 'origin/staging-site'
     add 81d2b5b5 Merge branch 'staging-site'
     add 084e7091 CloudFest blog (#180)
     add 40c6e331 integrations page
     add bcb8e76c Merge branch 'staging-site'
     add e3532c0b Update for cmk v6.4.0 (#189)
     add 58171be3 New cmk v6.4.0 blog (#191)
     add 7deef32a Merge branch 'staging-site'
     add 3eaa8689 Merge remote-tracking branch 'origin/staging-site'
     add e0df6e37 Revert b57ce72d45b670be13a4bbd14264650b6f8b877b.
     add 6a9d6009 Revert "Revert b57ce72d45b670be13a4bbd14264650b6f8b877b."
     add f2605c18 Merge remote-tracking branch 'origin/staging-site'
     add c3b94efe Merge remote-tracking branch 'origin/staging-site'
     add e3ffda8b Merge branch 'staging-site'
     add ccb16992 Merge remote-tracking branch 'origin/staging-site'
     add 83b9e9eb Merge branch 'main' into staging-site
     add 6eb7d94e captial to lower case p

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   (b0b3d4da)
            \
             N -- N -- N   refs/heads/staging-site (6eb7d94e)

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:

Reply via email to