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 1ca150e832b Regen for commit 9840bfde4e5fd0849ec025a5b0e68be003b51d4b
add 5e59604f9da Upgrade to JDK11 for CI Daily Deploy job
add 31c59ab989b CAMEL-18151: camel-jbang - Export should be a single
command making it easier to use from ci/cd
add 95c4bcff6e3 Regen for commit 31c59ab989b477f05a4ed5f8f844786ec6cfb403
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 (1ca150e832b)
\
N -- N -- N refs/heads/regen_bot (95c4bcff6e3)
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.deploy | 2 +-
.../main/java/org/apache/camel/dsl/jbang/core/commands/Export.java | 5 +++++
2 files changed, 6 insertions(+), 1 deletion(-)
