This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 52b536f830 Minor: Regenerated BOMs for
728aab6c56081863b61ab362a5279575b4253b91
add 5e223f95bc Re-enable test after
https://github.com/apache/tomee/pull/1093
add 23b127cb7b Minor: Regenerated BOMs for
5e223f95bcbb8ef7d6065ea511606e9e0e43fb85
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 (52b536f830)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(23b127cb7b)
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:
.../java/org/superbiz/moviefun/MoviesHtmlUnitTest.java | 15 ---------------
1 file changed, 15 deletions(-)
