This is an automated email from the ASF dual-hosted git repository.
jiahuili430 pushed a change to branch fix-changes-stats
in repository https://gitbox.apache.org/repos/asf/couchdb.git
omit a3d11b058 Remove deleted revs from `_conflicts` field
omit 0009d3a23 Avoid read docs twice when filtered _changes is triggered
omit 8efd6bced Verify the number of calls to `open_doc/3` when requesting
`_changes`
add 845ecdb11 Update fast_pbkdf2 to 1.0.6 (e7341dc) (#4966)
add b04735155 Exclude PPC64LE CI worker temporarily
add 1f77e2e36 Let's see if we can re-enable s390x again
add 2501fe69b PPC64LE worker is back online
add 51e6518a0 Verify the number of calls to `open_doc/3` when requesting
`_changes`
add 9f9c00fa8 Avoid read docs twice when filtered _changes is triggered
add 46b947327 Remove deleted revs from `_conflicts` field
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 (a3d11b058)
\
N -- N -- N refs/heads/fix-changes-stats (46b947327)
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.full | 16 +++++++---------
src/fast_pbkdf2/c_src/fast_pbkdf2.c | 4 ++--
src/fast_pbkdf2/rebar.config | 4 ++--
3 files changed, 11 insertions(+), 13 deletions(-)
