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 f152e443729 Regen for commit f7b7eb506d3a2edb77f252def2e36e659271780c
add efc0d358e9a Regen for commit f7b7eb506d3a2edb77f252def2e36e659271780c
(#10040)
add d8d23cb6456 (chores) cleanup: avoid setting the context twice
add 407e66d848e (chores) cleanup: use final variables where possible
add d69bfe844fd Regen for commit 611fd3359e94eaec276832c7001c1e585e4dddfc
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 (f152e443729)
\
N -- N -- N refs/heads/regen_bot (d69bfe844fd)
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/catalog/schemas/camel-spring.xsd | 7936 +++++++++++++-------
.../apache/camel/support/DefaultUuidGenerator.java | 4 +-
.../org/apache/camel/support/MessageSupport.java | 2 -
3 files changed, 5365 insertions(+), 2577 deletions(-)
