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 b6352e1  Regen for commit 3ae2425e56bfa81fd191007ea0b4f305388c25e5
    omit 3ae2425  Regen
    omit eeba23e  Update azure-storage-blob-component.adoc (#5535)
     add f1190af  Regen for commit 506561d54ce1a57b61788fff6b426041782dde2d

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

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/docs/azure-storage-blob-component.adoc | 48 +++++++++++-----------
 .../main/docs/azure-storage-blob-component.adoc    | 48 +++++++++++-----------
 .../ROOT/pages/azure-storage-blob-component.adoc   | 48 +++++++++++-----------
 3 files changed, 72 insertions(+), 72 deletions(-)

Reply via email to