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 64335482c8a Regen for commit 2f61cdf6f4e271e6c93d12058f712a4c2dda9ee3
add 0c655faefee Camel Azure Key Vault: Fixed javadoc
add 17e06a77623 Camel Azure Key Vault: Fixed javadoc
add ad7403a1bd2 Camel Azure Key Vault: Fixed Log
add 4b42b800002 Regen
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 (64335482c8a)
\
N -- N -- N refs/heads/regen_bot (4b42b800002)
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/component/azure/key/vault/EventhubsReloadTriggerTask.java | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
