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 7bb41db36a5 Regen for commit 0ea9f0eab41af67c36af6f11249be64a35f7c3e7
     add dd3fa683309 camel-jbang - Add load average statistics
     add 838646711ca Regen for commit d537cc7e089e641db82139027459e464c207da27 
(#8328)
     add c7089f77e2b Regen for commit 838646711ca8cad2b41cdfdb1b893ea8fce31f04

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   (7bb41db36a5)
            \
             N -- N -- N   refs/heads/regen_bot (c7089f77e2b)

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:
 .../core/commands/process/CamelContextTop.java     | 38 +++++++++++++-
 .../core/commands/process/CamelRouteStatus.java    | 58 ++++++++++++++--------
 .../jbang/core/commands/process/CamelRouteTop.java | 47 ++++++++++++++++++
 3 files changed, 122 insertions(+), 21 deletions(-)

Reply via email to