From 543039d190bfd74515b94187bdca5bbe52891488 Mon Sep 17 00:00:00 2001
From: Matthias Schiffer <mschiffer@universe-factory.net>
Date: Fri, 24 Dec 2021 14:22:20 +0100
Subject: [PATCH] docs: remove obsolete workaround for paragraphs in nested
 lists

With older versions of the RTD theme, paragraphs in nested lists would
lead to inconsistent spacing. This has been fixed, so we can remove our
workaround to use line blocks instead of paragraphs.
---
 docs/releases/v2019.1.1.rst | 14 ++++++++------
 docs/releases/v2019.1.2.rst | 14 ++++++++------
 docs/releases/v2019.1.3.rst | 14 ++++++++------
 docs/releases/v2019.1.rst   | 14 ++++++++------
 docs/releases/v2020.1.1.rst | 14 ++++++++------
 docs/releases/v2020.1.2.rst | 14 ++++++++------
 docs/releases/v2020.1.3.rst | 14 ++++++++------
 docs/releases/v2020.1.rst   | 14 ++++++++------
 8 files changed, 64 insertions(+), 48 deletions(-)

diff --git a/docs/releases/v2019.1.1.rst b/docs/releases/v2019.1.1.rst
index 2e173d7a1..024d5ad66 100644
--- a/docs/releases/v2019.1.1.rst
+++ b/docs/releases/v2019.1.1.rst
@@ -30,13 +30,15 @@ Known issues
 
 * The integration of the BATMAN_V routing algorithm is incomplete.
 
-  - | Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
-    | Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
-    | metric.
+  - Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
 
-  - | Throughput values are not correctly acquired for different interface types.
-    | (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
-    | This affects virtual interface types like bridges and VXLAN.
+    Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
+    metric.
+
+  - Throughput values are not correctly acquired for different interface types.
+    (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
+
+    This affects virtual interface types like bridges and VXLAN.
 
 * Default TX power on many Ubiquiti devices is too high, correct offsets are unknown
   (`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
diff --git a/docs/releases/v2019.1.2.rst b/docs/releases/v2019.1.2.rst
index 7231b4ef3..7ee0de325 100644
--- a/docs/releases/v2019.1.2.rst
+++ b/docs/releases/v2019.1.2.rst
@@ -26,13 +26,15 @@ Known issues
 
 * The integration of the BATMAN_V routing algorithm is incomplete.
 
-  - | Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
-    | Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
-    | metric.
+  - Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
 
-  - | Throughput values are not correctly acquired for different interface types.
-    | (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
-    | This affects virtual interface types like bridges and VXLAN.
+    Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
+    metric.
+
+  - Throughput values are not correctly acquired for different interface types.
+    (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
+
+    This affects virtual interface types like bridges and VXLAN.
 
 * Default TX power on many Ubiquiti devices is too high, correct offsets are unknown
   (`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
diff --git a/docs/releases/v2019.1.3.rst b/docs/releases/v2019.1.3.rst
index aab216931..7a78dfb26 100644
--- a/docs/releases/v2019.1.3.rst
+++ b/docs/releases/v2019.1.3.rst
@@ -36,13 +36,15 @@ Known issues
 
 * The integration of the BATMAN_V routing algorithm is incomplete.
 
-  - | Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
-    | Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
-    | metric.
+  - Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
 
-  - | Throughput values are not correctly acquired for different interface types.
-    | (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
-    | This affects virtual interface types like bridges and VXLAN.
+    Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
+    metric.
+
+  - Throughput values are not correctly acquired for different interface types.
+    (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
+
+    This affects virtual interface types like bridges and VXLAN.
 
 * Default TX power on many Ubiquiti devices is too high, correct offsets are unknown
   (`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
diff --git a/docs/releases/v2019.1.rst b/docs/releases/v2019.1.rst
index 6632b1190..43f5c3e75 100644
--- a/docs/releases/v2019.1.rst
+++ b/docs/releases/v2019.1.rst
@@ -253,13 +253,15 @@ Known issues
 
 * The integration of the BATMAN_V routing algorithm is incomplete.
 
-  - | Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
-    | Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
-    | metric.
+  - Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
 
-  - | Throughput values are not correctly acquired for different interface types.
-    | (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
-    | This affects virtual interface types like bridges and VXLAN.
+    Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
+    metric.
+
+  - Throughput values are not correctly acquired for different interface types.
+    (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
+
+    This affects virtual interface types like bridges and VXLAN.
 
 * Default TX power on many Ubiquiti devices is too high, correct offsets are unknown
   (`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
diff --git a/docs/releases/v2020.1.1.rst b/docs/releases/v2020.1.1.rst
index c78415315..e165863f9 100644
--- a/docs/releases/v2020.1.1.rst
+++ b/docs/releases/v2020.1.1.rst
@@ -25,13 +25,15 @@ Known issues
 
 - The integration of the BATMAN_V routing algorithm is incomplete.
 
-  - | Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
-    | Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
-    | metric.
+  - Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
 
-  - | Throughput values are not correctly acquired for different interface types.
-    | (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
-    | This affects virtual interface types like bridges and VXLAN.
+    Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
+    metric.
+
+  - Throughput values are not correctly acquired for different interface types.
+    (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
+
+    This affects virtual interface types like bridges and VXLAN.
 
 - Default TX power on many Ubiquiti devices is too high, correct offsets are unknown
   (`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
diff --git a/docs/releases/v2020.1.2.rst b/docs/releases/v2020.1.2.rst
index 4bc7c800c..378917eac 100644
--- a/docs/releases/v2020.1.2.rst
+++ b/docs/releases/v2020.1.2.rst
@@ -50,13 +50,15 @@ Known issues
 
 - The integration of the BATMAN_V routing algorithm is incomplete.
 
-  - | Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
-    | Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
-    | metric.
+  - Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
 
-  - | Throughput values are not correctly acquired for different interface types.
-    | (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
-    | This affects virtual interface types like bridges and VXLAN.
+    Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
+    metric.
+
+  - Throughput values are not correctly acquired for different interface types.
+    (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
+
+    This affects virtual interface types like bridges and VXLAN.
 
 - Default TX power on many Ubiquiti devices is too high, correct offsets are unknown
   (`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
diff --git a/docs/releases/v2020.1.3.rst b/docs/releases/v2020.1.3.rst
index 7b82b433e..7a9f5d8ec 100644
--- a/docs/releases/v2020.1.3.rst
+++ b/docs/releases/v2020.1.3.rst
@@ -30,13 +30,15 @@ Known issues
 
 - The integration of the BATMAN_V routing algorithm is incomplete.
 
-  - | Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
-    | Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
-    | metric.
+  - Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
 
-  - | Throughput values are not correctly acquired for different interface types.
-    | (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
-    | This affects virtual interface types like bridges and VXLAN.
+    Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
+    metric.
+
+  - Throughput values are not correctly acquired for different interface types.
+    (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
+
+    This affects virtual interface types like bridges and VXLAN.
 
 - Default TX power on many Ubiquiti devices is too high, correct offsets are unknown
   (`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
diff --git a/docs/releases/v2020.1.rst b/docs/releases/v2020.1.rst
index 8dd23630a..bebd07c4a 100644
--- a/docs/releases/v2020.1.rst
+++ b/docs/releases/v2020.1.rst
@@ -206,13 +206,15 @@ Known issues
 
 * The integration of the BATMAN_V routing algorithm is incomplete.
 
-  - | Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
-    | Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
-    | metric.
+  - Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
 
-  - | Throughput values are not correctly acquired for different interface types.
-    | (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
-    | This affects virtual interface types like bridges and VXLAN.
+    Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
+    metric.
+
+  - Throughput values are not correctly acquired for different interface types.
+    (`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
+
+    This affects virtual interface types like bridges and VXLAN.
 
 * Default TX power on many Ubiquiti devices is too high, correct offsets are unknown
   (`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
-- 
GitLab