This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/camel-website-pub.git
discard 58b2256cb Website updated to f485ca1b715885fdb4bca96abda1298bd630930e
discard b923d44bd Website updated to 325e929157412b27394080f4d4dba3d821476ddf
new b19eb21a3 Website updated to 325e929157412b27394080f4d4dba3d821476ddf
new cfd333c83 Website updated to a7b4929572b0e788c339e2301f4a26bd839fde20
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 (58b2256cb)
\
N -- N -- N refs/heads/asf-site (cfd333c83)
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 2 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:
.well-known/security.txt | 2 +-
releases/k-1.11.0/index.html | 4 +-
.../camel-spring-4.0.0-M1.xsd} | 0
site-manifest.json | 2 +-
sitemap-camel-core.xml | 8 +-
sitemap-camel-k.xml | 736 +--
sitemap-camel-kafka-connector.xml | 790 +--
sitemap-camel-kamelets.xml | 1672 ++---
sitemap-camel-karaf.xml | 62 +-
sitemap-camel-quarkus.xml | 3428 +++++-----
sitemap-camel-spring-boot.xml | 48 +-
sitemap-components.xml | 6652 ++++++++++----------
sitemap-manual.xml | 410 +-
13 files changed, 6907 insertions(+), 6907 deletions(-)
rename schema/{spring-xml/camel-spring-xml-4.0.0-M1.xsd =>
spring/camel-spring-4.0.0-M1.xsd} (100%)
