From bba2e4b4de668db525cbfdfc35292e5a0b51671a Mon Sep 17 00:00:00 2001
From: Michael Biebl <biebl@debian.org>
Date: Thu, 22 Feb 2024 17:21:11 +0100
Subject: New upstream version 1.46.0

---
 docs/api/html/settings-connection.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'docs/api/html/settings-connection.html')

diff --git a/docs/api/html/settings-connection.html b/docs/api/html/settings-connection.html
index f450a596..afd9d6cc 100644
--- a/docs/api/html/settings-connection.html
+++ b/docs/api/html/settings-connection.html
@@ -77,8 +77,8 @@ Depending on "connection.multi-connect", a profile can (auto)connect only once a
 </tr>
 <tr>
 <td><pre class="screen">autoconnect-ports</pre></td>
-<td><pre class="screen">NMTernary (int32)</pre></td>
-<td><pre class="screen"></pre></td>
+<td><pre class="screen">int32</pre></td>
+<td><pre class="screen">-1</pre></td>
 <td>Whether or not ports of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for controller connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave port connections untouched, 1: activate all the port connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-ports is read to determine the real value. If it is default as well, this fallbacks to 0.</td>
 </tr>
 <tr>
-- 
cgit 1.3.0-6-gf8a5