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 a54ab15 Regen for commit e638979343ada487aeb973898cf7bd7be47175ee
add 66e7869 CAMEL-16070: CamelContext - Restart via stop/start - Log a
WARN in case of restart. We have a bunch of tests that rely on being able to
stop/start such as clustering tests.
add 4af9018 Regen for commit e638979343ada487aeb973898cf7bd7be47175ee
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 (a54ab15)
\
N -- N -- N refs/heads/regen_bot (4af9018)
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:
.../main/java/org/apache/camel/impl/engine/AbstractCamelContext.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
