This is an automated email from the ASF dual-hosted git repository.

github-actions[bot] pushed a change to branch update-license-files
in repository https://gitbox.apache.org/repos/asf/storm.git


    omit 62560dde8 Regenerate license files after dependency changes
     add bc2b50623 build(deps): bump io.netty:netty-bom in /examples
     add 297e7715b Merge pull request #8927 from 
apache/dependabot/maven/examples/io.netty-netty-bom-4.2.16.Final
     add 9c061dd9d build(deps): bump io.netty:netty-bom from 4.2.15.Final to 
4.2.16.Final
     add 36debd0f1 Merge pull request #8933 from 
apache/dependabot/maven/io.netty-netty-bom-4.2.16.Final
     add fd81e18e4 Regenerate license files after dependency changes

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   (62560dde8)
            \
             N -- N -- N   refs/heads/update-license-files (fd81e18e4)

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:
 DEPENDENCY-LICENSES | 84 ++++++++++++++++++++++++++---------------------------
 LICENSE-binary      | 76 ++++++++++++++++++++++++------------------------
 pom.xml             |  2 +-
 3 files changed, 81 insertions(+), 81 deletions(-)

Reply via email to