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 96229e4  Regen for commit efe80be503469a0415cf52b0701311bea16e3341
     add fd8d755  Regen for commit efe80be503469a0415cf52b0701311bea16e3341
     add 5abe1c1cc Regen for commit fd8d7552a30804acaf1b7944afededc6191f849c

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   (96229e4)
            \
             N -- N -- N   refs/heads/regen_bot (5abe1c1cc)

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%)

Reply via email to