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 c7ae8131e0b Regen for commit 632e1da65509f82dbb2433eec401979bbb5759e1
     add b1d7d073f31 camel-jbang - Expose more details for health-checks.
     add 6cd54f408a8 Regen for commit b1d7d073f31a81e6d8ed0158461bec903d778b20

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   (c7ae8131e0b)
            \
             N -- N -- N   refs/heads/regen_bot (6cd54f408a8)

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:
 .../org/apache/camel/health/HealthCheckHelper.java | 35 +++++++++++++++++++++-
 .../camel/impl/console/HealthDevConsole.java       | 35 +++++++++++++++++-----
 .../camel/cli/connector/LocalCliConnector.java     | 19 +++++-------
 .../core/commands/process/CamelContextStatus.java  |  7 ++++-
 .../jbang/core/commands/process/ListProcess.java   |  7 ++++-
 5 files changed, 81 insertions(+), 22 deletions(-)

Reply via email to