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 ef94dc97be0 Regen for commit 03d0e9d64f863be87f57997d7ab74ee61084677e
add 6deca74000a Regen for commit 5c191c4189ef130be079439b9486c05705d6df43
add bf9041dd027 Camel-AWS2-S3: Improved Health Check with the invocation
of an head bucket operation instead of listing bucket
add ba50bdeca80 Regen for commit bf9041dd0271c150b32dc623863cd63900f41f49
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 (ef94dc97be0)
\
N -- N -- N refs/heads/regen_bot (ba50bdeca80)
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/aws2/s3/AWS2S3ConsumerHealthCheck.java | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
