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 c938f3e Regen for commit b8ac17dae4d8935148d5f59e53dca4a8f9e58126
add b060027 camel-sql - Upgrade javacc maven plugin
add 96b9309 Regen for commit b060027d0fd3e56f609f10a40b9435e7b9e16ddd
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 (c938f3e)
\
N -- N -- N refs/heads/regen_bot (96b9309)
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 +-
components/camel-sql/pom.xml | 2 +-
.../zookeeper/cloud/ZooKeeperServiceDiscoveryFactoryConfigurer.java | 6 ++----
parent/pom.xml | 2 +-
4 files changed, 5 insertions(+), 7 deletions(-)
