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 931be1d15e9 Regen for commit 0ed6c56517bd21078c815fc7db23e8050f0472a0
add 053b337193d Camel-Azure-Key-Vault docs: Fixed link
add b2c1ab662ee Regen
add 9b533750dd9 Regen for commit b2c1ab662eeb8c94859a7562606859dcf3dd64cf
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 (931be1d15e9)
\
N -- N -- N refs/heads/regen_bot (9b533750dd9)
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:
.../src/main/docs/azure-key-vault-component.adoc | 2 +-
.../dsl/KameletEndpointBuilderFactory.java | 220 ++++++++++-----------
2 files changed, 111 insertions(+), 111 deletions(-)
