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 5eb3f0acd0 Website updated to c02e9f94670d19b093ef35322380a54f30e44f0d
discard ec28bb9d86 Website updated to 325e929157412b27394080f4d4dba3d821476ddf
new 262a8b89f4 Website updated to 325e929157412b27394080f4d4dba3d821476ddf
new 5b7aa5abb2 Website updated to 872eb514aeb642f40279c3e7e40c7987c864dbb6
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 (5eb3f0acd0)
\
N -- N -- N refs/heads/asf-site (5b7aa5abb2)
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:
.htaccess | 326 +-
.well-known/security.txt | 2 +-
.../camel-spring-3.22.3.xsd} | 0
site-manifest.json | 2 +-
sitemap-camel-core.xml | 16 +-
sitemap-camel-k.xml | 1142 ++---
sitemap-camel-kafka-connector.xml | 888 ++--
sitemap-camel-kamelets.xml | 1474 +++---
sitemap-camel-karaf.xml | 12 +-
sitemap-camel-quarkus.xml | 2076 ++++-----
sitemap-camel-spring-boot.xml | 46 +-
sitemap-components.xml | 4712 ++++++++++----------
sitemap-manual.xml | 438 +-
13 files changed, 5567 insertions(+), 5567 deletions(-)
rename schema/{spring-xml/camel-spring-xml-3.22.3.xsd =>
spring/camel-spring-3.22.3.xsd} (100%)
