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


 discard b8f5d4b7e89 Regen for commit 4f75cd593d443556371e87cee02502eb2a43d310
     add 703ed4e3c40 CAMEL-20410: documentation fixes for camel-cassandraql
     add ec03e61427c CAMEL-20410: documentation fixes for camel-elasticsearch
     add f025cb9137e Regen for commit ec03e61427c0d95599f1253339c0dc639e0cb012

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

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:
 .../src/main/docs/cql-component.adoc               | 30 +++++++++++-----------
 .../src/main/docs/elasticsearch-component.adoc     | 22 ++++++++--------
 2 files changed, 26 insertions(+), 26 deletions(-)

Reply via email to