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 4aa01b8 Regen for commit f195b6edf8d9b8287ce2a8cbab16eb0874a391de
add 5a5bb57 Upgrade Hazelcast to version 4.1.1
add 6171475 sync deps
add e3c3611 Regen for commit 61714754813bb7a6c9b6e77ebeda49ff626a06ad
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 (4aa01b8)
\
N -- N -- N refs/heads/regen_bot (e3c3611)
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:
camel-dependencies/pom.xml | 2 +-
parent/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
