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 426aac9 Regen for commit c8fce55d4ba2a44b6f158d6b6cb1c40b9752cef6
add 39e3c2d camel-aws2-lambda: fixed broken link in component
documentation (#5125)
add eb937d7 Regen for commit 39e3c2dbbb700c24d102d3d185f75d43573ba3f8
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 (426aac9)
\
N -- N -- N refs/heads/regen_bot (eb937d7)
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:
.../resources/org/apache/camel/catalog/docs/aws2-lambda-component.adoc | 2 +-
components/camel-aws2-lambda/src/main/docs/aws2-lambda-component.adoc | 2 +-
docs/components/modules/ROOT/pages/aws2-lambda-component.adoc | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
