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

davisp pushed a change to branch COUCHDB-3287-pluggable-storage-engines
in repository https://gitbox.apache.org/repos/asf/couchdb.git.

     omits  559cd0b   TMP - Not sure when this should have disappeared
     omits  effa8bf   ss - implement pse
     omits  9f7829b   skip on rebase
     omits  52906e4   ss - add legacy engine
     omits  f2ac2b8   ss - implement pse
     omits  87441f8   Ensure deterministic revisions for attachments
     omits  73452d8   Add storage engine test suite
     omits  8288f7e   Implement pluggable storage engines
     omits  6129b7b   Add legacy storage engine implementation
       new  3beee8d   Add legacy storage engine implementation
       new  33a1d63   Implement pluggable storage engines
       new  4211100   Add storage engine test suite
       new  6375cd4   Ensure deterministic revisions for attachments

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   (559cd0b)
            \
             N -- N -- N   refs/heads/COUCHDB-3287-pluggable-storage-engines 
(6375cd4)

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 "omits" are not gone; other references still
refer to them.  Any revisions marked "discards" are gone forever.

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


Summary of changes:
 src/couch/src/couch_bt_engine.erl | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].

Reply via email to