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 d682b96e7f Website updated to ca96c175ec492e6cc1b0e2615be51ecca31e24b3
discard bbd2646b45 Website updated to f3436c8c5c39679c813eb319895f188289347c6c
new 1d8f876001 Website updated to f3436c8c5c39679c813eb319895f188289347c6c
new 97cb1a2ef6 Website updated to ca96c175ec492e6cc1b0e2615be51ecca31e24b3
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 (d682b96e7f)
\
N -- N -- N refs/heads/asf-site (97cb1a2ef6)
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 | 34 +-
.well-known/security.txt | 2 +-
site-manifest.json | 2 +-
sitemap-camel-core.xml | 16 +-
sitemap-camel-k.xml | 790 +++---
sitemap-camel-kafka-connector.xml | 450 ++--
sitemap-camel-kamelets.xml | 1504 ++++++------
sitemap-camel-karaf.xml | 16 +-
sitemap-camel-quarkus.xml | 1448 +++++------
sitemap-camel-spring-boot.xml | 46 +-
sitemap-components.xml | 4836 ++++++++++++++++++-------------------
sitemap-manual.xml | 458 ++--
12 files changed, 4801 insertions(+), 4801 deletions(-)
