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 178ac7707d6 Regen for commit 1897eee905ea3b9e8b037448f5941b6d9363e51b
add af5bbc8e2da camel-main - Polished
add 047efe60e22 Regen for commit af5bbc8e2da0d92faa2e72d32e58cea823531fe3
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 (178ac7707d6)
\
N -- N -- N refs/heads/regen_bot (047efe60e22)
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-main/src/main/java/org/apache/camel/main/MainSupport.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
