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 0476203a1 Remove support for delete markers
discard edd2d5cd4 Simplify logging of sensitive config values
discard 4dec13d2b Ensure these config tests get executed
discard 4a60c9946 Delete confusing test config delete reason
discard 4429aef3b Remove unused config field, export, include, defines
add bf6a827ed Reduce EUnit log noise
add a22d89499 Remove unused config field, export, include, defines
add 4637c0435 Delete confusing test config delete reason
add eb0516f4a Ensure these config tests get executed
add 7bbaacd32 Simplify logging of sensitive config values
add d7d2ba9b6 Remove support for delete markers
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 (0476203a1)
\
N -- N -- N refs/heads/config-delete-reload (d7d2ba9b6)
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/files/eunit.config | 2 +-
rel/files/eunit.ini | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
