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 fcd66dee8b5 Regen for commit 668ae0aa36551d16fdfce004fbbe41a6a5851a2c
add f66ed0918f1 Commercial Offering update
add c6d3d2c4448 Regen for commit f66ed0918f14b57aa8c36c8e45f7e6a894fcc5d5
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 (fcd66dee8b5)
\
N -- N -- N refs/heads/regen_bot (c6d3d2c4448)
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:
docs/user-manual/modules/ROOT/pages/commercial-camel-offerings.adoc | 5 +++++
1 file changed, 5 insertions(+)
