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

vgalaxies pushed a change to branch intro-commons
in repository https://gitbox.apache.org/repos/asf/incubator-hugegraph.git


    omit 7704f2c9e -Dmaven.test.skip=true
    omit 5a9382386 skipCommonsTests during other modules test
    omit aa7f60e06 include the stage repository
    omit 99a28465d update excludes for editorconfig-maven-plugin
    omit ddbadbe6a update .asf.yaml
    omit 3c75fdcbf upgrade to 1.5.0
    omit d04132e59 update .gitattributes
    omit 937ec0264 remove files
    omit c1af8caea regenerate known dependencies
    omit 551cc194e Merge branch 'master' into intro-commons
    omit dc3070f45 chore(dist): tar source and binary package for hugegraph 
with pd-store (#2594)
    omit af9469d62 reset to 1.3.0 for server
    omit 155de9c21 adapt CI
    omit a961c88f3 mvn editorconfig:format
    omit 68e58a048 basic adapt
     add 2fb950086 chore(commons): basic adapt for commons migration

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   (7704f2c9e)
            \
             N -- N -- N   refs/heads/intro-commons (2fb950086)

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:

Reply via email to