This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_notice_file_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/opennlp.git
omit fc3f6ff3 Minor: Regenerated NOTICE File for
9360ed095adbde52e1d40625e88f23b41bd7db4c
add cc1d362d [maven-release-plugin] prepare release opennlp-3.0.0-M2
add f9d250ba [maven-release-plugin] prepare for next development iteration
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 (fc3f6ff3)
\
N -- N -- N refs/heads/regenerate_notice_file_after_dep_upgrade
(f9d250ba)
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:
NOTICE | 2 +-
opennlp-distr/src/main/readme/NOTICE | 2 +-
opennlp-eval-tests/pom.xml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
