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 f4c3ccc0 Regen for commit fc25ff94e05f500db380bace10d6f728616c7266
add 04e578ed Adding Rhuan Rocha as contributor on site (#1036)
new e0afb11b Regen for commit 04e578ed60e747ec17a2443c97df97f429c006a4
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 (f4c3ccc0)
\
N -- N -- N refs/heads/regen_bot (e0afb11b)
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/community/team.md | 1 +
1 file changed, 1 insertion(+)
