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.


 discard 7727c4e  Regen for commit 998e7ed358b395f0186cd2b75e86d40eb664cb76
     add 115581d  CAMEL-17441: camel-health - Loading custom health-check from 
classpath scanning is not added to registry
     add 40595b4  Regen for commit 0ca042e3de2246802b8cfb1df38617b6ab1ff1c8 
(#6664)
     add 26e592d  Regen for commit 40595b44f61de2921b886ee540da9bef2ecbac73

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   (7727c4e)
            \
             N -- N -- N   refs/heads/regen_bot (26e592d)

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/impl/health/DefaultHealthCheckRegistry.java     | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

Reply via email to