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 aacbc7666ed Regen for commit 96a0438b1bb304fb5e92dae36c85a4e2273ecfa6
add a2298a28766 camel-jbang - Polished
add e8ce9d6417c Regen for commit 96a0438b1bb304fb5e92dae36c85a4e2273ecfa6
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 (aacbc7666ed)
\
N -- N -- N refs/heads/regen_bot (e8ce9d6417c)
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:
.../org/apache/camel/dsl/jbang/core/commands/process/ListEvent.java | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
