This is an automated email from the ASF dual-hosted git repository.

github-actions[bot] pushed a change to branch 
regenerate_notice_file_after_dep_upgrade_2.x
in repository https://gitbox.apache.org/repos/asf/opennlp.git


    omit 971b40948 Minor: Regenerated NOTICE File for 
2fe42dd993cc0b74ce12a45976cd67d39f74c1d2
     add 89f18bb2b [2.x]: Bump io.github.hakky54:logcaptor from 2.12.7 to 
2.13.0 (#1509)
     add 06d9d648e Minor: Regenerated NOTICE File for 
89f18bb2b547229b4b0778f3e54baf1f23b3a31e

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   (971b40948)
            \
             N -- N -- N   
refs/heads/regenerate_notice_file_after_dep_upgrade_2.x (06d9d648e)

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:
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Reply via email to