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 2d7c913bd86 Regen for commit efa24a173c09302d47f942c3ec3783b0b31cb8e9
omit efa24a173c0 Camel-18170 - Updating the Google Calendar component doc
(#7832)
add 33bb75d6236 Regen for commit 09b05a7417546e1eb6c997aff7f1b8855043e8d5
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 (2d7c913bd86)
\
N -- N -- N refs/heads/regen_bot (33bb75d6236)
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-3x-upgrade-guide-3_18.adoc | 5 -----
1 file changed, 5 deletions(-)
