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 627ade1 Regen for commit 1db62d1624ee5544e7f0f14c2de7627b995c3a75
add d92fd65 [CAMEL-17618]camel-ref: only add the endpoint into
camelContext when not exist (#6905)
add a8a01f1 CAMEL-17619 Remove the superfluous json-simple dependency
from the Slack component (#6904)
add e53bbe4 [CAMEL-17616] : improves row counting at
JdbcAggregateRepository startup (#6902)
add b339e09 Regen for commit d92fd6563ffca618340092d91a14e2296957641e
(#6910)
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 (627ade1)
\
N -- N -- N refs/heads/regen_bot (b339e09)
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/main/java/org/apache/camel/component/ref/RefEndpoint.java | 4 +++-
.../camel/processor/aggregate/jdbc/JdbcAggregationRepository.java | 8 ++++++--
2 files changed, 9 insertions(+), 3 deletions(-)
