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 aca8e30  Regen for commit c7c9de4a44299ef8cbc1aaaa67006281d05d9f1b
     add 1c44bb3  CAMEL-16265: camel-microprofile-metrics - Should mask 
sensitive endpoint uri.
     add 19d3042  Regen for commit 1c44bb3171343c50187f229b3f190105f7333f30

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   (aca8e30)
            \
             N -- N -- N   refs/heads/regen_bot (19d3042)

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:
 .../event/notifier/MicroProfileMetricsEventNotifierNamingStrategy.java | 3 ++-
 .../MicroProfileMetricsExchangeEventNotifierNamingStrategy.java        | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

Reply via email to