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 7e7c287a185 Regen for commit ba0f1c4e2b02bb37c785af8158e4e71f92ff0833
     add 66f1da1db22 CAMEL-18087: camel-core - Enable stream caching by 
default. (#7586)
     add 7d24ce778a2 CAMEL-17994 Camel-aws2-kinesis: Integration test does not 
work - KinesisComponentManualIT (#7591)
     add 2fd70bf1e7e Regen for commit 7d24ce778a235927133bafba6b9bcf6e8b093347

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   (7e7c287a185)
            \
             N -- N -- N   refs/heads/regen_bot (2fd70bf1e7e)

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:
 .../aws2/kinesis/integration/KinesisComponentManualIT.java          | 4 +---
 .../java/org/apache/camel/converter/stream/CachedOutputStream.java  | 6 +++---
 .../java/org/apache/camel/support/builder/OutputStreamBuilder.java  | 2 +-
 3 files changed, 5 insertions(+), 7 deletions(-)

Reply via email to