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 d8399549f80 Regen for commit 6b3a95d5b90f5bde4789959cbf1bf26c90ef5206
add 26a20e1015e Regen for commit dbdce79d2cdd3999e8a3af2ecd3985f71c00fba3
add e54e957d7b9 CAMEL-18907: camel-datasonnet
add e501e6425d4 Regen for commit e54e957d7b9367a45a3879ab85e0fe03e76656d6
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 (d8399549f80)
\
N -- N -- N refs/heads/regen_bot (e501e6425d4)
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/camel-4-migration-guide.adoc | 1 -
1 file changed, 1 deletion(-)
