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 7578350b1e Minor: Regenerated BOMs for
5cc170babd9d236b4427da9fcb1eed70c56668e3
add 3e08a53032 Remove useless comment
add f5cf3c67d0 Minor: Regenerated BOMs for
3e08a530327a11dc90aae47e9bc14a8bff35f698
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 (7578350b1e)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(f5cf3c67d0)
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:
assembly/pom.xml | 2 --
1 file changed, 2 deletions(-)
