This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_license_file_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/stormcrawler.git
omit cf3b188b Minor: Regenerated License File for
11083a624561729638db3c558154b1a04e3299db
add 05709662 Bump org.yaml:snakeyaml from 2.4 to 2.6
add 43db4cfe Minor: Regenerated License File for
057096628d10fcb279dee17b215ec8e7f5d191f5
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 (cf3b188b)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(43db4cfe)
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:
THIRD-PARTY.txt | 2 +-
core/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
