This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch kafka-s3-openshift-example
in repository https://gitbox.apache.org/repos/asf/camel-kamelets-examples.git
discard 48368c2 Kafka-S3 Example with Strimzi and Camel K operator on
openshift
discard 97f2f85 Kafka-S3 Example with Strimzi and Camel K operator on
openshift
discard dd6a3a2 Added the KameletBindings for testing
discard ae05598 Kafka-S3 Example with Strimzi and Camel K operator on
openshift
omit 2392478 Upgrade Dependencies in Azure-identity module in Azure Schema
Registry example
add b0c309a Upgrade Dependencies in Azure-identity module in Azure Schema
Registry example
new 6a69f43 Kafka-S3 Example with Strimzi and Camel K operator on
openshift
new 9d5cb6d Added the KameletBindings for testing
new a385ba3 Kafka-S3 Example with Strimzi and Camel K operator on
openshift
new 11cd20b Kafka-S3 Example with Strimzi and Camel K operator on
openshift
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 (48368c2)
\
N -- N -- N refs/heads/kafka-s3-openshift-example (11cd20b)
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 4 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:
