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 033aee0b1f Website updated to caad5f5eb66e092d9ccde22598a95fc35d866de9
discard 682eba5f6c Website updated to 325e929157412b27394080f4d4dba3d821476ddf
new 28a1e18c52 Website updated to 325e929157412b27394080f4d4dba3d821476ddf
new 3aa8fe97ad Website updated to 2b3c5a2958fd774100d752e3972527edc6755507
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 (033aee0b1f)
\
N -- N -- N refs/heads/asf-site (3aa8fe97ad)
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 | 130 +-
.well-known/security.txt | 2 +-
.../camel-spring-3.22.2.xsd} | 0
site-manifest.json | 2 +-
sitemap-camel-core.xml | 14 +-
sitemap-camel-k.xml | 904 +--
sitemap-camel-kafka-connector.xml | 824 +--
sitemap-camel-kamelets.xml | 1402 ++---
sitemap-camel-karaf.xml | 24 +-
sitemap-camel-quarkus.xml | 2026 +++----
sitemap-camel-spring-boot.xml | 56 +-
sitemap-components.xml | 5776 ++++++++++----------
sitemap-manual.xml | 426 +-
13 files changed, 5793 insertions(+), 5793 deletions(-)
rename schema/{spring-xml/camel-spring-xml-3.22.2.xsd =>
spring/camel-spring-3.22.2.xsd} (100%)
