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


 discard 6eaf5ed27 Regenerate license files after dependency changes
     add 8009caad1 build(deps): bump com.github.ben-manes.caffeine:caffeine in 
/examples
     add 4cc584a24 Merge pull request #9204 from 
apache/dependabot/maven/examples/com.github.ben-manes.caffeine-caffeine-3.3.1
     add 63d48e6df build(deps): bump org.xerial.snappy:snappy-java in /examples
     add acae783ac Merge pull request #9206 from 
apache/dependabot/maven/examples/org.xerial.snappy-snappy-java-1.1.10.12
     new 665a829b8 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   (6eaf5ed27)
            \
             N -- N -- N   refs/heads/update-license-files (665a829b8)

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.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 DEPENDENCY-LICENSES | 2 +-
 LICENSE-binary      | 2 +-
 pom.xml             | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

Reply via email to