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 faac9ab5 Regen for commit 31a27fc112370878b02b4bab926ff17e1da01de5
     add 499d5195 Add missing release info for Camel Quarkus 3.0.0-RC1 (#1043)
     new c6a0673a Regen for commit 499d5195b1e47d29709a0051d6a2267627d4a14c

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   (faac9ab5)
            \
             N -- N -- N   refs/heads/regen_bot (c6a0673a)

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.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 content/releases/q/release-3.0.0-RC1.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 content/releases/q/release-3.0.0-RC1.md

Reply via email to