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-website.git
omit 3ee8a6e3 Regen for commit 37a9bf78aeeaab3f3c5ef553a7f013b70aaa3cbe
add 4d5c7b0a Add release notes and blog entry for Camel 4.0.0-RC2
add 879571a8 Regen for commit 4d5c7b0a46299ee1a164e8249ff0b9c4beab2de0
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 (3ee8a6e3)
\
N -- N -- N refs/heads/regen_bot (879571a8)
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:
.../07/RELEASE-4.0.0-RC2}/camel-featured.jpg | Bin
.../07/RELEASE-4.0.0-RC2}/index.md | 11 +++++------
content/releases/release-4.0.0-RC2.md | 16 ++++++++++++++++
3 files changed, 21 insertions(+), 6 deletions(-)
copy content/blog/{2019/09/RELEASE-3.0.0-RC1 =>
2023/07/RELEASE-4.0.0-RC2}/camel-featured.jpg (100%)
copy content/blog/{2020/06/RELEASE-3.4.0 =>
2023/07/RELEASE-4.0.0-RC2}/index.md (61%)
create mode 100644 content/releases/release-4.0.0-RC2.md
