This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 4eeb90daa39 Regen for commit 761ac58b6100b832b5943ea108e4a04d0ca1b7f9
add f5b9096b16d (chores) ci: use Strimzi images for testing Kafka code on
s390x
add 0fbbf1df752 Update AtlasMap to version 2.3.18
add df568700dd9 Regen for commit 0fbbf1df752beaf55aa076863e52078658201abd
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 (4eeb90daa39)
\
N -- N -- N refs/heads/regen_bot (df568700dd9)
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.
No new revisions were added by this update.
Summary of changes:
Jenkinsfile.s390x | 3 ++-
camel-dependencies/pom.xml | 2 +-
parent/pom.xml | 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
