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 66cb59f Regen for commit 4a7722072c6db6d298ab06f8fa4e4cfe2fa0fda8
add 490452a Regen for commit 4a7722072c6db6d298ab06f8fa4e4cfe2fa0fda8
add f4ae71a Regen for commit 490452a9cc1de034c6b6e04e1e0806c6fab88fd4
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 (66cb59f)
\
N -- N -- N refs/heads/regen_bot (f4ae71a)
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/org/apache/camel/catalog/others.properties | 1 +
.../generated/resources/org/apache/camel/catalog/others}/console.json | 0
2 files changed, 1 insertion(+)
copy {core/camel-console/src/generated/resources =>
catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/others}/console.json
(100%)
