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

yuchenhe pushed a change to branch v2.1
in repository https://gitbox.apache.org/repos/asf/incubator-pegasus.git.


    omit b6bf1aa  Release pegasus 2.1.0-RC1
     new 839826d  fix: Load options from file when open an exist DB (#587)
     new a83343d  fix: Use default options to open db when latest option file 
has incompatible db options (#593)
     new 4276c2c  fix: fix db is not nullptr when release_db (#594)
     new c0389ae  refactor: update license statement (#600)
     new 4f8db17  Release pegasus 2.1.0-RC1

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   (b6bf1aa)
            \
             N -- N -- N   refs/heads/v2.1 (4f8db17)

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.

The 5 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 README.md                                    |   2 +-
 src/server/meta_store.cpp                    |  58 ++++++++--
 src/server/meta_store.h                      |  12 ++
 src/server/pegasus_server_impl.cpp           | 160 ++++++++++++++++++++-------
 src/server/pegasus_server_impl.h             |  10 +-
 src/server/test/pegasus_server_impl_test.cpp |  53 ++++++++-
 6 files changed, 245 insertions(+), 50 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to