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

vatamane pushed a change to branch pre-3.5.1-amalgam
in repository https://gitbox.apache.org/repos/asf/couchdb.git


 discard 77269bcbb Doc updates for 3.5.1
 discard c74f3c335 Bump version to 3.5.1
 discard 1151e22b8 Cherry-pick main changes into 3.5.x
     add c62ac8fb1 Cherry-pick main changes into 3.5.x
     add 08fb2f8df Bump version to 3.5.1
     add 51339d421 Doc updates for 3.5.1

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   (77269bcbb)
            \
             N -- N -- N   refs/heads/pre-3.5.1-amalgam (51339d421)

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:
 rel/overlay/etc/default.ini                        |    5 +
 share/server/views.js                              |    4 +-
 src/couch/src/couch_proc_manager.erl               |    2 +
 src/couch/src/couch_query_servers.erl              |    9 +-
 src/couch/test/eunit/couch_query_servers_tests.erl |   22 +-
 .../patches/01-spidermonkey-185-mode.patch         |    6 +-
 src/couch_quickjs/patches/02-test262-errors.patch  |   10 +-
 src/couch_quickjs/quickjs/quickjs-opcode.h         |   11 +-
 src/couch_quickjs/quickjs/quickjs.c                | 1524 ++++++++++++--------
 src/couch_quickjs/quickjs/test262_errors.txt       |   16 +-
 src/docs/src/config/query-servers.rst              |   10 +
 src/docs/src/whatsnew/3.5.rst                      |    5 +-
 12 files changed, 998 insertions(+), 626 deletions(-)

Reply via email to