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 8c9d52531e6 Regen for commit 396b7b69bb707e2bcd9010b18b6c78ed5144f77f
add 504c1c2205f Regen for commit 4a3fe6aa91e001a2522fa02ade00e9c2905d3fc3
(#9441)
add c74d9e04e9f (chores) camel-main: use log markers for a warning message
add 9d6b5e6b434 (chores) camel-base-engine: delay checking if the exchange
failed
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 (8c9d52531e6)
\
N -- N -- N refs/heads/regen_bot (9d6b5e6b434)
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/impl/engine/DefaultUnitOfWork.java | 3 +--
.../src/main/java/org/apache/camel/main/MainDurationEventNotifier.java | 2 +-
2 files changed, 2 insertions(+), 3 deletions(-)
