This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch camel-master
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git.
discard a6bbbb3 Aggregation Support: Changed option name from
camel.beans.aggregation to camel.aggregation
omit 09d6240 Align to 3.6.0-SNAPSHOT
omit b7659dd Changelog on camel-master should push on camel-master
omit a97f95c Point to 3.6.0-SNAPSHOT
add 469642b MongoDB Kafka Connector: In the docs add Json as base value
converter
add a46dc82 Regen docs
new cecc292 Point to 3.6.0-SNAPSHOT
new 2be8253 Changelog on camel-master should push on camel-master
new 3d6f698 Align to 3.6.0-SNAPSHOT
new 8f83e35 Aggregation Support: Changed option name from
camel.beans.aggregation to camel.aggregation
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 (a6bbbb3)
\
N -- N -- N refs/heads/camel-master (8f83e35)
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.
The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../src/main/docs/camel-mongodb-kafka-sink-connector.adoc | 7 +++++++
1 file changed, 7 insertions(+)
