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 ee804f7 Regen for commit d45a22acb72df632a3a90cb339e31fcf2866babf
add 432194a (chores) camel-atlasmap: cleanups
add f1ead9c [CAMEL-16108] The S3 metadata is included in the Exchange as
a Header
add 2d1e4f1 [CAMEL-16108] docs added
add 0b11963 Regen for commit 2d1e4f17f09c37490134aca99f362698d577c4ad
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 (ee804f7)
\
N -- N -- N refs/heads/regen_bot (0b11963)
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/catalog/docs/aws2-s3-component.adoc | 29 +++++++++++-----------
.../camel/component/atlasmap/AtlasMapEndpoint.java | 6 ++---
.../src/main/docs/aws2-s3-component.adoc | 29 +++++++++++-----------
.../camel/component/aws2/s3/AWS2S3Constants.java | 1 +
.../camel/component/aws2/s3/AWS2S3Endpoint.java | 1 +
.../modules/ROOT/pages/aws2-s3-component.adoc | 29 +++++++++++-----------
6 files changed, 50 insertions(+), 45 deletions(-)
