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 4f0ba17 Regen for commit e61df2eb964b94a4bd78ad9e30f222103131ce87
omit e61df2e fixed duplicate leveldb
add 955408d Regen for commit 1c6f15797ccc5e455a92bfef610a16f28f367000
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 (4f0ba17)
\
N -- N -- N refs/heads/regen_bot (955408d)
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 | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy components/{camel-leveldb =>
camel-leveldb-legacy}/src/generated/resources/leveldb.json (100%)
