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 6b2edf41957 Regen for commit b11fb0b47c16c90c9d87cd51a4b560b9d6e62a60
     add 217360c22b0 (chores) camel-gora: cleaned unnecessary unboxing/boxing
     add 83734ce2233 (chores) camel-hyperledger-aries: cleaned unnecessary 
unboxing/boxing
     add e96579203ab (chores) camel-resteasy: cleaned unnecessary 
unboxing/boxing
     add ad31a1f1322 (chores) camel-vertx: cleaned unnecessary unboxing/boxing
     add 4e908af5056 Regen for commit b11fb0b47c16c90c9d87cd51a4b560b9d6e62a60

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   (6b2edf41957)
            \
             N -- N -- N   refs/heads/regen_bot (4e908af5056)

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:
 .../apache/camel/component/gora/GoraConsumer.java  |  2 +-
 .../CredentialDefinitionsServiceHandler.java       | 25 ++++++++--------------
 .../servlet/ResteasyServletInputStreamCopier.java  |  2 +-
 .../operations/VertxKafkaProducerOperations.java   |  2 +-
 4 files changed, 12 insertions(+), 19 deletions(-)

Reply via email to