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 c9ef3f6598c Regen for commit 87fcf18b4096fa306d804eef0dacff7a5d52c208
     add 8ffe5153784 Regen for commit 87fcf18b4096fa306d804eef0dacff7a5d52c208 
(#8808)
     add 758c74859e2 CAMEL-18776: camel-hdfs - Fix HdfsNormalFileHandler to 
handle temporary file path correctly (#8803)
     add a2117d698c2 Regen for commit 758c74859e2b123723b48806422a88afce206380

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   (c9ef3f6598c)
            \
             N -- N -- N   refs/heads/regen_bot (a2117d698c2)

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:
 catalog/camel-allcomponents/pom.xml                                     | 2 +-
 .../java/org/apache/camel/component/hdfs/HdfsNormalFileHandler.java     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

Reply via email to