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 4009a4271b9 Regen for commit 59429f6652cd32c3e1a3fad60ab5ad79438e2267
     add 1df9912a4df CAMEL-19047 CamelTestSupport (junit5) - some checks does 
not work with ContextPerClass (#9346)
     add f76dda76d88 Regen for commit 1df9912a4df774b91d2db34de8209000fda599f7

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   (4009a4271b9)
            \
             N -- N -- N   refs/heads/regen_bot (f76dda76d88)

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:
 .../src/main/java/org/apache/camel/test/junit5/CamelTestSupport.java | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

Reply via email to