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 e0abac6 Regen for commit d2b0862eba4c9613aca35e10a71027ec5d90f2a7
add 6a1d982 CAMEL-16462: camel-core - Optimize RecipientList EIP to
reduce object allocations.
add e2faf88 CAMEL-16462: camel-core - Optimize RecipientList EIP to
reduce object allocations.
add 1e4b501 CAMEL-16462: camel-core - Optimize RecipientList EIP to
reduce object allocations.
add 75a3463 CAMEL-16462: camel-core - Optimize Multicast EIP to reduce
object allocations.
add ac5da44 Regen for commit 75a34636810791ed2407d2e6a687637e012aad4d
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 (e0abac6)
\
N -- N -- N refs/heads/regen_bot (ac5da44)
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:
.../apache/camel/processor/MulticastProcessor.java | 40 ++----
.../org/apache/camel/processor/RecipientList.java | 43 +-----
.../camel/processor/RecipientListProcessor.java | 148 ++++++++++++++-------
.../java/org/apache/camel/processor/Splitter.java | 2 +-
.../apache/camel/support/cache/ServicePool.java | 29 ++--
.../java/org/apache/camel/util/ObjectHelper.java | 3 +
6 files changed, 138 insertions(+), 127 deletions(-)
