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 fc28fe6d95c Regen for commit c76e3f1811bc5430974928cdbbf4e9b0eee033dd
add 8f0b6ab5907 CAMEL-19062 - Clean up Parent POM - Junit Pioneer
add 8a52fd668b9 CAMEL-19062 - Clean up Parent POM - Junit Pioneer
add 2a1908bd6e3 Regen for commit 8a52fd668b9073901e0124e26a054ea272f69e4b
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 (fc28fe6d95c)
\
N -- N -- N refs/heads/regen_bot (2a1908bd6e3)
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:
core/camel-management/pom.xml | 1 +
parent/pom.xml | 5 -----
2 files changed, 1 insertion(+), 5 deletions(-)
