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/opennlp.git
discard 9a8f33dd Minor: Regenerated NOTICE File for
a680e0ec38690cd4ae89d0bdc90821e83d1dd3e0
add 0b2af34e OPENNLP-1747: Update build-helper-maven-plugin to 3.6.1 (#795)
add 9e0cd703 Minor: Regenerated NOTICE File for
0b2af34e8ff961575c5cb1acb4aa9ab795beccaa
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 (9a8f33dd)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(9e0cd703)
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:
opennlp-core/opennlp-runtime/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
