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 e4e32b853 Regenerate license files after dependency changes
add adf06cfe0 build(deps): bump com.github.luben:zstd-jni in /examples
add 8d6f7828c Merge pull request #8960 from
apache/dependabot/maven/examples/com.github.luben-zstd-jni-1.5.7-12
add a4c7f9bf1 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 (e4e32b853)
\
N -- N -- N refs/heads/update-license-files (a4c7f9bf1)
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:
