Remove another metion of RISC-V and promise another update

diff --git a/updates/022_2020feb14_openpower_eula_released.mdwn b/updates/022_2020feb14_openpower_eula_released.mdwn
index a589320bf9391c5b3c13740de9b630363a9c34d4..ccbf5f4cb0b874862690c1fa0fce23f2ffb75d1c 100644 (file)
--- a/updates/022_2020feb14_openpower_eula_released.mdwn
+++ b/updates/022_2020feb14_openpower_eula_released.mdwn
@@ -84,13 +84,8 @@ simply *implementing* existing RISC-V Standards?," and he replied, "all
 of them."  I then asked, "how many of those projects are *innovating*,
 developing alternative extensions to what is dictated by the RISC-V
 Foundation?" With the answer being "none," *that* was the point at which
-he understood the extent of the problem, and (with the systematic failure
-to respond to in-good-faith requests to participate in innovation),
-how the RISC-V Foundation - and its members, by way of them having
-"voting power" and thus having direct influence over how the RISC-V Foundation
-is run - are at risk of violating EU anti-trust legislation, particularly
-given that NLNet's funds for our project come *directly from an EU Horizon
-2020 Grant*.
+he understood the extent of the problem. I'll publish a more comprehensive
+update on this topic soon.
 
 ### Meeting Other LibreSOC People