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 f9d7014 Regen for commit 642730785b459a93c0ceec6809e900a6b3fcfa9f
add 2bd9b1f Upgrade to apache spark 3.2.1
add b583be9 Regen for commit 2bd9b1f077fae82f62b25f34f939b58dbae67c03
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 (f9d7014)
\
N -- N -- N refs/heads/regen_bot (b583be9)
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 +-
.../resources/org/apache/camel/catalog/others.properties | 1 -
.../org/apache/camel/catalog/others/console.json | 15 ---------------
parent/pom.xml | 2 +-
4 files changed, 2 insertions(+), 18 deletions(-)
delete mode 100644
catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/others/console.json
