This is an automated email from the ASF dual-hosted git repository.
dahn pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/cloudstack-www.git
discard 961f7d44d Added 4.20 api docs (#262) (#263)
add 798582271 Added 4.20 api docs (#262)
add 79ca6c46a blog: fix grammar, spelling and whitespace in Markdown files
(#249)
add 72c13d36f move past events (#265)
add 80f9919b9 Bump http-proxy-middleware from 2.0.6 to 2.0.7 (#256)
add 4fa3d53bf source release verification instructions (#260)
add 39722c316 Bump cross-spawn from 7.0.3 to 7.0.6 (#261)
add e039ad8a1 Update the name of our organization (#264)
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 (961f7d44d)
\
N -- N -- N refs/heads/main (e039ad8a1)
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:
...8-apache-cloudstack-lts-maintenance-release1.md | 2 +-
...dstack-collaboration-conference-2022-roundup.md | 8 ++--
.../index.md | 2 +-
.../index.md | 2 +-
blog/2023-09-18-cloudstack-4.18.1-release/index.md | 2 +-
blog/2023-12-07-ccc2023-roundup/index.md | 2 +-
.../index.md | 2 +-
.../index.md | 2 +-
blog/2024-09-01-Committing-to-the-future/index.md | 4 +-
src/components/Events/index.tsx | 45 ++++++++--------------
src/pages/downloads.mdx | 10 +++++
src/pages/users.mdx | 2 +-
yarn.lock | 12 +++---
13 files changed, 46 insertions(+), 49 deletions(-)
