This is an automated email from the ASF dual-hosted git repository.
rnewson pushed a change to branch score-order-fix
in repository https://gitbox.apache.org/repos/asf/couchdb.git
discard b59b79d5b default order is by relevance (high to low)
add 8771fbd67 Merge 3.5.1 change to main
add 439033c37 Bump Erlang versions and clean up a few things
add 6a0df0686 upgrade gradle and spotless for JDK25 compat
add 3c48d7f9a Merge pull request #5738 from apache/nouveau-25
add 16852e363 default order is by relevance (high to low)
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 (b59b79d5b)
\
N -- N -- N refs/heads/score-order-fix (16852e363)
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:
build-aux/Jenkinsfile | 48 +------
nouveau/build.gradle | 24 ++--
nouveau/gradle/wrapper/gradle-wrapper.properties | 2 +-
.../org/apache/couchdb/nouveau/core/IOUtils.java | 2 +-
src/docs/src/config/misc.rst | 7 +-
src/docs/src/whatsnew/3.5.rst | 145 +++++++++++++++++++++
version.mk | 2 +-
7 files changed, 170 insertions(+), 60 deletions(-)
