This is an automated email from the ASF dual-hosted git repository.
rnewson pushed a change to branch jenkins-enable-nouveau-ci
in repository https://gitbox.apache.org/repos/asf/couchdb.git
discard d6a0ae809 mango end-to-end tests for nouveau
discard 54422f8bf enhance out of order message
discard 62cea7500 Add log dumping to build-report make target
discard d5fa5f577 OTP 23 support
discard 41acc02de allow PUT to existing index if definition identical
discard e50d34f8a enable nouveau tests in CI
add eeca93c94 declare dependency on nouveau
add e4bc2b51c Merge pull request #4550 from apache/mango-nouveau-dep
add 07d5fa650 enable nouveau tests in CI
add c982b5179 allow PUT to existing index if definition identical
add 594be1bb5 OTP 23 support
add d1cd2fb7f Add log dumping to build-report make target
add 00789824c enhance out of order message
add 83fc0e391 mango end-to-end tests for nouveau
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 (d6a0ae809)
\
N -- N -- N refs/heads/jenkins-enable-nouveau-ci (83fc0e391)
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:
src/mango/src/mango.app.src | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
