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.
discard 54e8dd5 Regen for commit 58fefda671acb0a9f8dc3de2a11c3bd16ce9d9d4
add 8dd13d2 Moved Jenkinsfile.jdk11 file as standard build for Camel
add 239e264 Regen for commit 8dd13d2f2e7cee07aad081ebee07e6f4415cbd9b
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 (54e8dd5)
\
N -- N -- N refs/heads/regen_bot (239e264)
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:
Jenkinsfile | 16 ++-------
Jenkinsfile.jdk11 | 100 ------------------------------------------------------
2 files changed, 2 insertions(+), 114 deletions(-)
delete mode 100644 Jenkinsfile.jdk11
