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 e4bbd174455 Regen for commit 6754c349574b6697efe4a86628c2468b2b943e90
add ee30f3a0c0c CAMEL-20410: documentation fixes for camel-elytron
add 79d28df6a95 CAMEL-20410: documentation fixes for camel-etcd3
add c38ed8985df CAMEL-20410: documentation fixes for camel-exec
add 7feaef511f0 CAMEL-20410: documentation fixes for camel-fastjson
add f6666ff21b5 CAMEL-20410: documentation fixes for camel-fhir
add 0e2ae17daa9 CAMEL-20410: documentation fixes for camel-file-watch
add 1968a54e4e9 Regen for commit 0e2ae17daa929662cc52694b3aefa4cc15bbff44
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 (e4bbd174455)
\
N -- N -- N refs/heads/regen_bot (1968a54e4e9)
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:
.../camel-elytron/src/main/docs/elytron.adoc | 31 ++++++++-------
.../camel-etcd3/src/main/docs/etcd3-component.adoc | 45 +++++++++++-----------
.../camel-exec/src/main/docs/exec-component.adoc | 42 ++++++++++----------
.../src/main/docs/fastjson-dataformat.adoc | 9 ++---
.../src/main/docs/fhir-component.adoc | 2 +-
.../src/main/docs/file-watch-component.adoc | 5 ++-
6 files changed, 70 insertions(+), 64 deletions(-)
