This is an automated email from the ASF dual-hosted git repository.
jin pushed a change to branch release-1.0.0
in repository
https://gitbox.apache.org/repos/asf/incubator-hugegraph-toolchain.git
discard b0b130aa fix gpg signature error & remove redundant configs
omit a7959fb4 Merge branch 'master' into release-1.0.0
omit 1c47673e switch binary path to target (#396)
omit d8c16f70 refact: update release script and fix bug
omit 2fcda519 Merge branch 'master' into before-release
omit 07aec9e0 chore: ignore generate package files & update pom
omit 1c616628 feat: support release apache package by script
omit f6dce523 chore: add ignore files in .gitattributes
add 770b6647 chore: add ignore files in .gitattributes
add 1b461fa7 feat: support release apache package by script
add f73bd445 chore: ignore generate package files & update pom
add 20840d87 refact: update release script and fix bug
add fb676864 switch binary path to target (#396)
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 (b0b130aa)
\
N -- N -- N refs/heads/release-1.0.0 (fb676864)
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:
hugegraph-client/pom.xml | 129 ++++++++++++++--------------
hugegraph-hubble/hubble-dist/pom.xml | 1 -
hugegraph-loader/pom.xml | 162 +++++++++++++++++------------------
hugegraph-tools/pom.xml | 38 ++++----
pom.xml | 158 ++++++++++++++++++----------------
5 files changed, 250 insertions(+), 238 deletions(-)
