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.
omit 955408d Regen for commit 1c6f15797ccc5e455a92bfef610a16f28f367000
add e61df2e fixed duplicate leveldb
add dfaae15 Remove jmh converter test from camel-core as we have that in
tests/camel-jmh instead
add 707846e Regen for commit dfaae1551834a777b466b466c74516b54e1565f3
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 (955408d)
\
N -- N -- N refs/heads/regen_bot (707846e)
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:
.../src/generated/resources/leveldb.json | 15 --
core/camel-core/pom.xml | 12 --
.../camel/converter/ConverterBenchmarkTest.java | 155 ---------------------
3 files changed, 182 deletions(-)
delete mode 100644
components/camel-leveldb-legacy/src/generated/resources/leveldb.json
delete mode 100644
core/camel-core/src/test/java/org/apache/camel/converter/ConverterBenchmarkTest.java
