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 69258f9b4f2 Regen for commit 08c89e34d1d7587757a0489216f18e93c80e1a4b
add f20e20b0ec6 CAMEL-15105: move ExchangeFactory ownership to the context
extension
add eedaeb8b4bc CAMEL-15105: move ProcessorExchangeFactory ownership to
the context extension
add 5053b173622 CAMEL-15105: move ExchangeFactoryManager ownership to the
context extension
add 407d706819b Regen for commit f00421ba1d4ba544fdec516231a90f65cbb150af
add b5f1acf80dc Regen for commit 407d706819ba94db90ee4630ae3336f3dc2c080f
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 (69258f9b4f2)
\
N -- N -- N refs/heads/regen_bot (b5f1acf80dc)
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/impl/engine/AbstractCamelContext.java | 14 ---------
.../impl/engine/DefaultCamelContextExtension.java | 33 ++++++++++++----------
2 files changed, 18 insertions(+), 29 deletions(-)
