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 4edfd6e9dff Regen for commit 8db9d8fb48fde943c79c72571c9b5494c7975e6b
add f1b16e6c493 CAMEL-18448: camel-jbang - Capture number of reloads
add 79d1d0eae58 Regen for commit 9ac710a353492689ed30a9dd9e2d3ed66771ca3d
(#8257)
add 895e292bf66 Regen for commit 79d1d0eae58dae1e1a3cb87bfea7ecd374e084d0
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 (4edfd6e9dff)
\
N -- N -- N refs/heads/regen_bot (895e292bf66)
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/dsl/jbang/core/commands/process/CamelContextStatus.java | 4 ++++
1 file changed, 4 insertions(+)
