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 28d35c3 Regen for commit 4b91a7583bc9802f6ee6c79aaab2e779e72eccf5
omit 4b91a75 Update azure-cosmosdb-component.adoc
add 5b5113c Regen for commit 48c68058c03459a0c4a9438e75ecb9efe7381654
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 (28d35c3)
\
N -- N -- N refs/heads/regen_bot (5b5113c)
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-azure-cosmosdb/src/main/docs/azure-cosmosdb-component.adoc | 2 +-
docs/components/modules/ROOT/pages/azure-cosmosdb-component.adoc | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
