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 4aa8e2aa6bf Regen for commit 5f1ee7e0952dd5917e43eec3796d992a36d43142
add 95380d2313c CAMEL-19159 - Camel-AWS: Support Profile Credential
provider as configuration - AWS Lambda
add 791667c3f88 CAMEL-19159 - Camel-AWS: Support Profile Credential
provider as configuration - AWS Lambda
add a235985ecda Regen for commit aa6c27791c7d843e0137b90a0e84a1d8140596ed
add c214af7ffaa Regen for commit a235985ecdaf57a3f6a2d75555e82263aba4839c
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 (4aa8e2aa6bf)
\
N -- N -- N refs/heads/regen_bot (c214af7ffaa)
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:
.../impl/Lambda2ClientIAMProfileOptimizedImpl.java | 21 +++------------------
1 file changed, 3 insertions(+), 18 deletions(-)
