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 9cd972315d5 Regen for commit 20f90ddacd2ea715d70e5a1eb450eb03f2a76f07
add 71cd00dda29 Moving camel-jbang to version 3.20.5 for container image
add 8e098ec3528 Regen for commit 71cd00dda299dbaf01d37e513471aa683e004f1a
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 (9cd972315d5)
\
N -- N -- N refs/heads/regen_bot (8e098ec3528)
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:
dsl/camel-jbang/camel-jbang-container/Dockerfile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
