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

jaydoane pushed a change to branch config-delete-reload
in repository https://gitbox.apache.org/repos/asf/couchdb.git


 discard 0f727cd1e fixup: simplify using `is_map_key` in guard
 discard a2f1ffa5a Remove support for delete markers
 discard 7c6a72b37 Simplify logging of sensitive config values
 discard 0ca1990fd Ensure these config tests get executed
 discard 1277545e5 Delete confusing test config delete reason
 discard 48f528f9d Remove unused config field, export, include, defines
     add fe49416b5 Add extra rev tree changes tests
     add ce2769777 Git ignore all `.hypothesis` directories
     add 4073d9d5f Remove unused config field, export, include, defines
     add 8e1495fdf Delete confusing test config delete reason
     add 832489f5e Ensure these config tests get executed
     add 7d6d7b1ad Simplify logging of sensitive config values
     add 4027591f4 Remove support for delete markers
     add b919b5736 fixup: simplify using `is_map_key` in guard

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   (0f727cd1e)
            \
             N -- N -- N   refs/heads/config-delete-reload (b919b5736)

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:
 .gitignore                                   |   2 +-
 src/couch/test/eunit/couch_changes_tests.erl | 245 +++++++++++++++++++++++----
 2 files changed, 215 insertions(+), 32 deletions(-)

Reply via email to